Josh Triplett

:+1: for attempting to detect and diagnose this case, when looking for a trait impl for a tuple.

Link to my comment about `repr(system)` and either removing it or changing it to `repr(windows)` or `repr(MSVC)`: - https://github.com/rust-lang/rfcs/pull/3718#discussion_r2035946897

FCPing this. T-lang, do we have consensus that we don't want to have issues on the rfcs repo used to report feature requests? (There are enough other places for feature...

This seems reasonable. I've wanted this a few times myself, and it's always inconvenient to work around. It looks like the issue of edition handling has been addressed, and the...

While it might make sense to have an argument to specify a query explicitly, what I'm looking for here is an automatic guessing of whether something needs a search. `rustup...

Ideally, it does a search of std internally (rather than just forwarding the query), so that it knows there's a result to open. If an argument would otherwise error, and...

@ChrisDenton That would mean users have to know that they can't search for a method name. It's still an improvement over the status quo, though.

Is the only concern about automatic searching the possible performance issue of searching many documentation files? If the design was such that the performance of that search were good, would...

Rather than just `tokio::task::yield_now().await`, could there be some defined procedure to more explicitly shut down the connection and make sure the other end gets a chance to see that? Obviously...

Linking to a planned policy change in a thread comment, so that it's easier to find: https://github.com/rust-lang/rfcs/pull/3660#discussion_r1854135667