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
What I am saying is, treating things as individual resources is slow, whether implicit or explicit. Fast programs do things in bulk and e.g. free memory in large batches at specific times. It could be possible that this style of type constraint could be leveraged on
that type of memory use, and if that's actually helpful, that'd be interesting. But to be honest the "as fast as a very slow C program" claims get old after a while (I don't mean from you, they are common across academia and industry).
Yeah I understand, I'm saying that it's not obvious but you can use ATS' proof system to batch up frees into a compile time list of linear resources and discharge them whenever you want. You're not forced to take a free at end of scope or whatever.
That would probably have been a more motivating example now that think about it ...
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
