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
Example in Rust: there's arguments for encoding: allocation, nounwind, simd (and which parts), float usage, atomic usage, i/o, purity, constexpr, thread-affinity, and probably others. This is a lot of things to guarantee/care about!
I vaguely lean towards the C answer here. Public API is what's documented. I `#[nodoc]` everything I don't want to be relied on (and in rare cases just mention in the docs "you shouldn't rely on X"). Of course you still have to consider "does this actually break code" on changes
right but I'm specifically talking about a world where everyone wants you to interoperate with dozens of (potentially adhoc) effects. Every effect you incidentally satisfy that you refuse to document makes your library less useful.
Yup, this is the world I live in. I think it's easy to over-estimate how bad it is, as long as you actively consider "what realistically could break" with every change, and take the spirit of RFC 1105 to heart.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
