Fix type parameter default error to mention type and trait definitions#30997
Merged
bors merged 1 commit intorust-lang:masterfrom Jan 23, 2016
Merged
Fix type parameter default error to mention type and trait definitions#30997bors merged 1 commit intorust-lang:masterfrom
bors merged 1 commit intorust-lang:masterfrom
Conversation
Contributor
Author
Contributor
|
r? @brson (rust_highfive has picked a reviewer for you, use r? to override) |
src/librustc_typeck/collect.rs
Outdated
Contributor
There was a problem hiding this comment.
Seems like if we're going to try and be exhaustive, we ought to include type aliases too. I also think we should add trait into the list with struct and enum, like so: "defaults for type parameters are only allowed in struct, enum, type, or trait definitions".
Introduced in PR rust-lang#30724, needs to mention that type parameter defaults are legal in trait and type definitions too.
Contributor
Author
|
Good idea, I've updated it to say exactly that. |
Contributor
Collaborator
|
📌 Commit 9d77694 has been approved by |
Contributor
|
@bors rollup |
Collaborator
|
⌛ Testing commit 9d77694 with merge b78b9ae... |
bors
added a commit
that referenced
this pull request
Jan 23, 2016
Fix type parameter default error to mention type and trait definitions Introduced in PR #30724, needs to mention that type parameter defaults are legal in trait and type definitions too.
steveklabnik
added a commit
to steveklabnik/rust
that referenced
this pull request
Jan 23, 2016
Fix type parameter default error to mention type and trait definitions Introduced in PR rust-lang#30724, needs to mention that type parameter defaults are legal in trait and type definitions too.
steveklabnik
added a commit
to steveklabnik/rust
that referenced
this pull request
Jan 23, 2016
Fix type parameter default error to mention type and trait definitions Introduced in PR rust-lang#30724, needs to mention that type parameter defaults are legal in trait and type definitions too.
Collaborator
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fix type parameter default error to mention type and trait definitions
Introduced in PR #30724, needs to mention that type parameter defaults
are legal in trait and type definitions too.