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
I don't know that I can give a better answer than "it depends". Maybe you should ask an Idris programmer. ;) For Diesel we work around this by "the public API for the result of this method is this helper type w/ the same name". Associated type values are generally private
r.e. your list of things worth encoding, I think the only one that's really worth doing is constexpr and maybe i/o purity (I generally always lean towards "this type does I/O, other types take this one as an arg" regardless so I don't care as much)
I do think that *in general* spending a lot of time considering how changes will affect your users goes a very long way. If everybody in OSS did this, we would have a lot fewer of these discussions
There's a lot of value in having a connection with your larger users, and being able to just ask "hey does this commit break your app?". Crater is nice, but ultimately the real breakage is from the servos of the world, and apps of that size are rarely open source.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
