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
The problem is that element-by-element "resource" tracking is inherently very slow. So "as fast as a very slow C program" is not a particularly appealing statement. But people do not want to hear this because it goes against decades of convention. Sadly the convention is bad.
Furthermore, "resource leak" kinds of problems are a very tiny minority of the bugs faced by serious projects in production, so expending a large amount of programming effort on them is unwarranted. Help with the real problems would be great though.
If this doesn't sound like it makes sense (which it probably doesn't), I explain for a few minutes here:https://youtu.be/uZgbKrDEzAs?t=602 …
In ATS resource handling is explicit, you have to explicitly close the file nothing done behind the scenes. Also no implicit frees like RAII, you have to explictly call it. Linear types can also be used for concurrency. But I'm not a game dev so maybe don't have the same needs.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
