Skip to content
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

Closed
brson opened this issue Jul 17, 2014 · 6 comments
Closed

Tracking RFC 11 - bounded struct typarams #15759

brson opened this issue Jul 17, 2014 · 6 comments
Milestone

Comments

@brson
Copy link
Contributor

brson commented Jul 17, 2014

https://github.com/rust-lang/rfcs/blob/master/active/0011-bounded-type-parameters.md

Nominating.

@pcwalton
Copy link
Contributor

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. :(

@pnkfelix
Copy link
Member

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.)

@pnkfelix
Copy link
Member

assigning P-high, not 1.0 milestone.

@brson
Copy link
Contributor Author

brson commented Jul 24, 2014

This needs a volunteer to implement.

@pcwalton
Copy link
Contributor

Nominating for 1.0 P-backcompat-lang due to the desire to use this in important types like HashMap.

@pnkfelix
Copy link
Member

P-backcompat-lang, 1.0

@pnkfelix pnkfelix added this to the 1.0 milestone Aug 14, 2014
pcwalton added a commit that referenced this issue Aug 16, 2014
them during kind checking.

This implements RFC #11.

Closes #15759.
bors added a commit that referenced this issue Aug 17, 2014
them during kind checking.

This implements RFC #11.

Closes #15759.

r? @nikomatsakis
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 a pull request may close this issue.

3 participants