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
Thinking about how that would work in practice. User goes to i32 or vector, and looks at the methods it provides. Are you saying don't show the common methods in the list but rather on a separate page?
I was asking about where the knowledge of being able to do .into() on the given type should live in the docs. Sounds like you were commenting on something else?
I think showing `Into` impls is super useful, but we don't need to show that a type can be converted into itself over and over again.
Sounds like maybe we're talking about two different things?
I'm referring to the screenshot above which shows `impl<T> From<T> for T`, `impl<T> Borrow<T> for T`, `impl<T> Any for T`, and the transitive impls from that. These aren't terribly useful to know in the first place, and just don't need to be repeated on *every* type
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
