-
Notifications
You must be signed in to change notification settings - Fork 13.4k
add Iterable traits #7597
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
This is not yet possible due to issues (including ICEs) related to lifetimes. At least some are already reported, but I'll look into this more. |
This version of Iterable does not apply to |
@blake2-ppc: yup, but it gets really problematic if you omit the |
Triage bump. |
See also erickt's RFC proposing a somewhat similar design with additional convenience methods. |
I think this should be closed (or moved to rust-lang/rfcs) since it requires an accepted RFC to be implemented, and there are two RFCs that address this issue: rust-lang/rfcs#17 (Iterable) and rust-lang/rfcs#235 (Collection reform). |
This issue has been moved to the RFCs repo: rust-lang/rfcs#397 |
assertions_on_constants: ignore indirect `cfg!` Fixes rust-lang#7597 changelog: [`assertions_on_constants`] ignore constants indirectly based on `cfg!`
Something like the following:
In the future we can define default methods like
enumerate
when method resolve is fixed. #5898The text was updated successfully, but these errors were encountered: