-
Notifications
You must be signed in to change notification settings - Fork 13.4k
decide if we should do backtracking in impl resolution #4148
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Comments
Fixing this is a bit of a doozy, but it needs to be done anyhow. This basically requires rewriting the impl res. strategy to be "backtracking". That is, in order to decide if the method |
Bumping to 0.7 |
Seems non-critical for 0.7. Nominating for milestone 3, feature-complete. |
cc #5527 |
accepted as well defined |
Triage bump |
Still an unfixed as of 2460170. I updated the code to the latest syntax:
|
Triage bump. Updated example (kept it close to the original one).
|
This issue is really not relevant anymore. Trait reform implemented backtracking and more. |
This is the next thing blocking removal of iter-trait:
The text was updated successfully, but these errors were encountered: