-
Notifications
You must be signed in to change notification settings - Fork 13.3k
Ungate associated types, globs and default type parameters #20568
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
Conversation
r? @nick29581 (rust_highfive has picked a reviewer for you, use r? to override) |
r? @aturon, @nikomatsakis (Will rebase) |
I think we should unfeature gate |
Unboxed closures are more subtle, since there's features that we want to still have gated for 1.0 (e.g. writing |
@japaric Note that you don't need |
They work pretty well now, and the stdlib is using them everywhere so they're impossible to avoid anyway.
These are in scope for 1.0, so this is good to e.g. make it easier find bugs.
These are in scope for 1.0, and this is good to e.g. find as many bugs as possible.
These aren't in their final form, but are all aiming to be part of 1.0, so at the very least encouraging usage now to find the bugs is nice. Also, the widespread roll-out of associated types in the standard library indicates they're getting good, and it's lame to have to activate a feature in essentially every crate ever.
Landed in #20610. |
These aren't in their final form, but are all aiming to be part of 1.0, so at the very least encouraging usage now to find the bugs is nice.
Also, the widespread roll-out of associated types in the standard library indicates they're getting good, and it's lame to have to activate a feature in essentially every crate ever.