Skip to content

Use correct generic names when printing error messages #29315

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

Closed
zrneely opened this issue Oct 26, 2015 · 1 comment
Closed

Use correct generic names when printing error messages #29315

zrneely opened this issue Oct 26, 2015 · 1 comment
Labels
A-diagnostics Area: Messages for errors, warnings, and lints

Comments

@zrneely
Copy link

zrneely commented Oct 26, 2015

I'm sure the title is far too generic (no pun intended), but I'm not sure what else to call it.

Here's an example of the issue: http://is.gd/SpT2Db

It would be nice for new Rust users if we could see, in the error message, the name of the generic whose type could not be inferred, either like this:

error: unable to infer enough type information about `A`; type annotations or generic parameter binding required [E0282]

or like this:

 Foo::<A>::baz();

or even this:

Foo::<_>::baz();

I think any of these would be useful for a new Rust user - as it is, it's easy to get frustrated - "Where's my use of _? There's nothing to fix!"

@huonw huonw added the A-diagnostics Area: Messages for errors, warnings, and lints label Oct 26, 2015
@nagisa
Copy link
Member

nagisa commented Jan 19, 2016

Duplicate of #25633

@nagisa nagisa closed this as completed Jan 19, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-diagnostics Area: Messages for errors, warnings, and lints
Projects
None yet
Development

No branches or pull requests

3 participants