You can add location information to your Tweets, such as your city or precise location, from the web and via third-party applications. You always have the option to delete your Tweet location history. Learn more
So mold as a daemon would be *perfect* in that case.
But I mean, this is just an insane amount of complexity for something that should be trivial.
i had assumed that part of it was trivial because you can just mark the symbols as weak right? The linker doesn't actually care if it finds all the symbols? I assumed patching the relocations was the hard part and using incremental link would constrain the problem
Marking symbols as weak is not enough, otherwise you'd get duplicates. At the very least, those take up unnecessary space in every patch, but they also would mess with debugger symbols.
It could be trivial, but unfortunately isn't with the current tools we have. If every symbol access went through a PLT or GOT, hot-reloading would be much easier. Or were you thinking about something else? Would love to hear your take on that.
Symbol lookup is just matching a name to a value. This is something we know how to make computers do very fast. Those symbols are a small amount of data, e.g. the symbol for a function is much smaller than the code in almost all cases, and requires no computation whereas the code
This was my first though actually. Imagine to combine them and fix bugs.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
