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

resolve: import resolution diagnostics #32849

Merged
merged 3 commits into from
Apr 12, 2016

Conversation

jseyfried
Copy link
Contributor

This improves the diagnostics for failing import resolutions (fixes #32833).
r? @eddyb

// option. This file may not be copied, modified, or distributed
// except according to those terms.

use bar::Foo; //~ ERROR There is no `Foo` in `bar` [E0432]
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This error message used to include the nonsensical suggestion Did you mean to use Foo?

@eddyb
Copy link
Member

eddyb commented Apr 9, 2016

@bors r+ rollup

@bors
Copy link
Contributor

bors commented Apr 9, 2016

📌 Commit 44ddaa2 has been approved by eddyb

Manishearth added a commit to Manishearth/rust that referenced this pull request Apr 10, 2016
…tics, r=eddyb

resolve: import resolution diagnostics

This improves the diagnostics for failing import resolutions (fixes rust-lang#32833).
r? @eddyb
steveklabnik added a commit to steveklabnik/rust that referenced this pull request Apr 11, 2016
…tics, r=eddyb

resolve: import resolution diagnostics

This improves the diagnostics for failing import resolutions (fixes rust-lang#32833).
r? @eddyb
bors added a commit that referenced this pull request Apr 11, 2016
Rollup of 9 pull requests

- Successful merges: #32768, #32802, #32815, #32823, #32849, #32854, #32862, #32870, #32873
- Failed merges:
@bors bors merged commit 44ddaa2 into rust-lang:master Apr 12, 2016
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.

“There is no X in ???. Did you mean to use X?”
3 participants