Skip to content

Improve error message for variant values used as types #27085

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

Merged
merged 1 commit into from
Jul 18, 2015

Conversation

Ryman
Copy link
Contributor

@Ryman Ryman commented Jul 17, 2015

This also changes how variant values are printed in errors, they are no
longer printed in their parent scope. As far as I can tell, this is
leftover from pre-namespacing of enums.

Closes #17546.

This also changes how variant values are printed in errors, they are no
longer printed in their parent scope. As far as I can tell, this is
leftover from pre-namespacing of enums.

Closes rust-lang#17546.
@rust-highfive
Copy link
Contributor

r? @pcwalton

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

@alexcrichton
Copy link
Member

@bors: r+ b416762

Thanks!

bors added a commit that referenced this pull request Jul 18, 2015
This also changes how variant values are printed in errors, they are no
longer printed in their parent scope. As far as I can tell, this is
leftover from pre-namespacing of enums.

Closes #17546.
@bors
Copy link
Collaborator

bors commented Jul 18, 2015

⌛ Testing commit b416762 with merge 3f50dca...

@bors bors merged commit b416762 into rust-lang:master Jul 18, 2015
nham pushed a commit to nham/rust that referenced this pull request May 17, 2016
Manishearth added a commit to Manishearth/rust that referenced this pull request May 19, 2016
Add regression tests for error message when using enum variant as a type

I'm guessing these were actually fixed with PR rust-lang#27085.

Closes rust-lang#21225
Closes rust-lang#19197
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