-
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
Tracking RFC 11 - bounded struct typarams #15759
Comments
Do we have a plan for how to implement this? The RFC doesn't specify how to do it, and this is…a lot of work because of the way vtables work. I'm a little unhappy with the scope creep here. :( |
Since this is almost entirely unimplemented, there are no current 1.0 blocking parts of it. (if we were to implement it only partially, then it would become a backwards compatibiilty risk.) |
assigning P-high, not 1.0 milestone. |
This needs a volunteer to implement. |
Nominating for 1.0 P-backcompat-lang due to the desire to use this in important types like HashMap. |
P-backcompat-lang, 1.0 |
them during kind checking. This implements RFC #11. Closes #15759. r? @nikomatsakis
https://github.com/rust-lang/rfcs/blob/master/active/0011-bounded-type-parameters.md
Nominating.
The text was updated successfully, but these errors were encountered: