Uh oh!
There was an error while loading. Please reload this page.
Allow bounds on type variables in enums & structs - #13302
Conversation
huonw
commented
Apr 4, 2014
It might be good to have a negative test like: structFoo<X:TraitDoesntExist>;enumBar<X:TraitDoesntExist>{}traitTrait<T>{}structBaz<X:Trait<Invalid>>;enumQux<X:Trait<Invalid>>{}traitTrait2<'a>{}structBaz2<X:Trait<'a>>;enumQuz2<X:Trait<'a>>;fnmain(){}just making sure that the bounds are being resolved correctly (i.e. the non-existent traits/params/lifetimes are being correctly error about). I guess having a (valid) |
alexcrichton
commented
Apr 4, 2014
Note that the corresponding RFC has not yet been merged. This should likely wait until it is merged. |
nrc
commented
Apr 5, 2014
Now with more tests. |
Does not do any checking of bounds, just allows them to exist.
nrc
commented
Apr 24, 2014
The RFC for this has been accepted. r? |
alexcrichton
commented
Apr 30, 2014
Like the RFC, I'm not sure how useful or expected this is unless the type bounds themselves are checked. I don't think that we're gaining much by merging this before the type bounds are checked, and it seems small enough (surprisingly!). Perhaps merging this should wait until the type checking has been implemented? |
flaper87
commented
May 3, 2014
I agree with @alexcrichton It may be confusing to be able to specify type bounds and then realize they're not checked. Lets wait for the type checking to be implemented. |
nrc
commented
May 3, 2014
Yeah, it is not useful until we do the checking. But we do need it for that. Happy to wait for the checking before we land this. |
alexcrichton
commented
May 3, 2014
OK, in that case I'm going to close this for now until the checking is implemented as well. |
Don't auto-publish lib crates I believe this should *just* work? With this cargo-workspaces should not consider them
Rustup r? ghost changelog: none
Does not do any checking of bounds, just allows them to exist. Checking will come later