Skip to content

compiler "did you mean" tips don't include macros: unresolved name panic. Did you mean self? #19788

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.

Sign up for GitHub

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

Jump to bottom
Closed
imbaczek opened this issue Dec 12, 2014 · 3 comments
Closed

compiler "did you mean" tips don't include macros: unresolved name panic. Did you mean self? #19788

imbaczek opened this issue Dec 12, 2014 · 3 comments
Labels
A-diagnostics Area: Messages for errors, warnings, and lints A-macros Area: All kinds of macros (custom derive, macro_rules!, proc macros, ..)

Comments

@imbaczek
Copy link

e.g.

error: unresolved name `panic`. Did you mean `self`?

it'd be helpful if the compiler could also check if there's a macro with that name and suggest that if so.
@bombless
Copy link
Contributor

And I think type mismatch tips that vec! macro report can directly points out the line number.

@kmcallister kmcallister added A-macros Area: All kinds of macros (custom derive, macro_rules!, proc macros, ..) A-diagnostics Area: Messages for errors, warnings, and lints labels Jan 16, 2015
@nham
Copy link
Contributor

nham commented Jun 22, 2015

This seems to be a dupe of #5780

@alexcrichton
Copy link
Member

Indeed!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
A-diagnostics Area: Messages for errors, warnings, and lints A-macros Area: All kinds of macros (custom derive, macro_rules!, proc macros, ..)
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@imbaczek @alexcrichton @kmcallister @nham @bombless