-
Notifications
You must be signed in to change notification settings - Fork 12.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
don't use generator witness for implied bounds #115173
Conversation
@bors try |
⌛ Trying commit d06f509 with merge c998a0147310b58319f4172e953bf2a9c5c5c5fa... |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
💔 Test failed - checks-actions |
@bors try |
⌛ Trying commit 7d78764 with merge 3ba53ac6e3a6cb265590cf8c832c06260d624b6e... |
☀️ Try build successful - checks-actions |
@craterbot check |
👌 Experiment ℹ️ Crater is a tool to run experiments across parts of the Rust ecosystem. Learn more |
🚧 Experiment ℹ️ Crater is a tool to run experiments across parts of the Rust ecosystem. Learn more |
🎉 Experiment
|
@aliemjay any updates on this? |
Closing this as inactive. Feel free to reöpen this pr or create a new pr if you get the time to work on this. Thanks |
...
and also don't draw implied bounds from the output type of generators and closures. FnDef is still an exception so that we keep supporting(edit: reverted):TODO open issues for the bugs fixed here. In the mean time there is
tests/ui/async-await/generator-wf-check.rs
r? @ghost