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

rustc: make error messages containing generic more self-explanatory. #11513

Merged
merged 1 commit into from
Jan 13, 2014

Conversation

huonw
Copy link
Member

@huonw huonw commented Jan 13, 2014

Unsuffixed literals like 1 and 1.1, and free type parameters sometimes
have to be printed in error messages, which ended up with ,
and . This change puts the words "generic" and "integer"/"float"
into the message so it's not a completely black box.

Unsuffixed literals like 1 and 1.1, and free type parameters sometimes
have to be printed in error messages, which ended up with <V0>, <VI0>
and <VF0>. This change puts the words "generic" and "integer"/"float"
into the message so it's not a completely black box.
bors added a commit that referenced this pull request Jan 13, 2014
Unsuffixed literals like 1 and 1.1, and free type parameters sometimes
have to be printed in error messages, which ended up with \<V0>, \<VI0>
and \<VF0>. This change puts the words "generic" and "integer"/"float"
into the message so it's not a completely black box.
@bors bors closed this Jan 13, 2014
@bors bors merged commit e25d706 into rust-lang:master Jan 13, 2014
@huonw huonw deleted the generic-errs branch June 27, 2014 06:48
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.

4 participants