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
Memory bugs are to be avoided, but are a small minority of the number of bugs total. Most bugs are just due to complexity. So “memory safety” is kind of a red herring; if you fix a small number of bugs by gaining memory safety, but in doing so increase friction too much, it is
easily a net loss, because the other 95% of bugs are harder to deal with. Our solution is to provide customizable metaprogramming techniques you can leverage to help with all 100% of bugs, as you feel is best for your own domain and program.
Interesting! As someone who works in a highly logic-bug sensitive field (clinical analysis), I've found that having an advanced type system, incl. memory ownership, is almost always a benefit in reducing logic bugs, as well as memory bugs; have you had a different experience?
Also: a recent post from the maintainer of curl seems to contradict these numbers. Is it possible your experience is not universal here?
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
