scottmcm

Let's give it a shot! @bors try @rust-timer queue

> does this affect the codegen in practical circumstances? Would be good to have codegen tests to demonstrate what this is doing -- especially since that way there's a way...

Note that the listed motivation ```rust if let mx = max() && mx < usize::MAX { /* */ } ``` could of course be written as ```rust if let mx...

Hmm, I worry that this would muddy the "items are items" thing, because now typing the same thing will work differently in different places, which seems non-great. I wonder about...

@Nadrieril Good point! The majority case there is just `.map_err(Into::into)` -- I've added a section. We could probably do something similar for residual-to-residual conversion too, though it's unclear how commonly...

@joshtriplett I originally just put lang, but then thought "well but I did put traits in here", so added libs-api too in case. You're absolutely right that my intent here...

@crumblingstatue See this part of the future possibilities section in the RFC: https://github.com/scottmcm/rfcs/blob/if-at-first-you-dont-succeed/text/3721-homogeneous-try-blocks.md#annotated-heterogeneous-try-blocks Basically, probably not with the annotation where you had it in your example, but yes in a...

> We were happy to see experimental work proceed that would help with refining the RFC. Posted https://github.com/rust-lang/rust/pull/148725 to implement the proposed behaviour on nightly. It confirms that none of...

> We might want to provide a `generate_where_bounds` macro: I don't think this is possible from tokens. To me, these are the reasonable options: - Bound all the type parameters,...

As someone who doesn't like this lint, 👍 But also, to try to be constructive about it, I think there are also ways it could be made warn-by-default again. For...