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
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.
Do you think this philosophy would be tractable in a world of pervasive dependent typing?
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
Alternate answer: Claim every change is fixing a soundness bug.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
