Skip to content

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

Closed
wants to merge 6 commits into from

Conversation

huonw
Copy link
Member

@huonw huonw commented Jan 5, 2015

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.

@rust-highfive
Copy link
Contributor

r? @nick29581

(rust_highfive has picked a reviewer for you, use r? to override)

@huonw
Copy link
Member Author

huonw commented Jan 5, 2015

r? @aturon, @nikomatsakis

(Will rebase)

@rust-highfive rust-highfive assigned aturon and unassigned nrc Jan 5, 2015
@japaric
Copy link
Member

japaric commented Jan 5, 2015

I think we should unfeature gate unboxed_closures as well, since they are more stable than associated_types.

@huonw
Copy link
Member Author

huonw commented Jan 5, 2015

Unboxed closures are more subtle, since there's features that we want to still have gated for 1.0 (e.g. writing Fn<(int,), ()> instead of Fn(int)).

@aturon
Copy link
Member

aturon commented Jan 6, 2015

@japaric Note that you don't need unboxed_closures to use unboxed closures; you only need it for direct access to the Fn* traits.

huonw added 6 commits January 6, 2015 14:15
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.
alexcrichton added a commit to alexcrichton/rust that referenced this pull request Jan 6, 2015
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.
@huonw
Copy link
Member Author

huonw commented Jan 6, 2015

Landed in #20610.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants