Esteban Kuber

Any thoughts on this output? text version ``` error[E0599]: the function or associated item `do_something` exists for tuple `(i32, &u32, String)`, but its trait bounds were not satisfied --> traits-on-tuples.rs:24:43...

@weiznich very important points. Yes, we should have a limit on how many things we try. I think an example of the second case would be useful and should be...

@fmease I guess that this ticket is enough. > Rust's errors are bad at telling you "you have this trait error specifically because this specific trait bound required by this...

The `must_not_suspend` lint seems tangentially related. That one is to ensure that a value doesn't go through a `yield` point, while this is so that we don't call `std::thread::sleep` in...

> I am curious if these can be unified futher It might be that this annotation on functions *could* influence the logic of the `must_not_suspend` lint. > worst case `must_not_suspend`...

> what functions besides `std::thread::sleep()` can be reliably marked as `#[diagnostic::blocking]`? Effectively most of `std::io` and `std::fs`. Even `println!()` should likely be considered as a no-no from an `async fn`,...

> I expect some uses of `Mutex` and similar to not count as blocking, e.g. the following should not count imho In the way that I'm doing analysis today, that...

Sigh, clippy shows at least one test where a suggestion causes there to be a condition that isn't a `bool` but rather a type where `Not` returns a `bool`. We...

@pnkfelix we can keep the current (undocumented) behavior by making the desugaring be ```rust { let x: bool = !!condition; x } ``` instead of what this PR does: ```rust...

I tried the marker trait approach for