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

Improve diagnostics E0425: use (public) name #34379

Merged
merged 1 commit into from
Jun 25, 2016
Merged

Conversation

liigo
Copy link
Contributor

@liigo liigo commented Jun 20, 2016

E0425: unresolved name

@rust-highfive
Copy link
Collaborator

r? @nikomatsakis

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

@@ -843,6 +843,15 @@ Or:
let unknown_variable = 12u32;
let x = unknown_variable; // ok!
```

Please verify that the name is declared by `use` item and ensure it's public
Copy link
Member

Choose a reason for hiding this comment

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

I'd say: "If the item isn't available in the current module, please check you imported it:".

@liigo
Copy link
Contributor Author

liigo commented Jun 21, 2016

@GuillaumeGomez Thank you! I've updated (and rebased).

bar();
```

...and check the item is public, non-private at least, to the current module.
Copy link
Member

Choose a reason for hiding this comment

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

"... and check if the item is public, non-private at least, to the current module."

Copy link
Contributor Author

@liigo liigo Jun 22, 2016

Choose a reason for hiding this comment

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

https://is.gd/8CFKu9
when use globs, rustc doesn't tells user if an item is private

Copy link
Member

Choose a reason for hiding this comment

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

It was just because you forgot a whitespace after "...".

@liigo
Copy link
Contributor Author

liigo commented Jun 22, 2016

updated (and rebased)


... and check if the item is public, non-private at least, to the current
module.

Copy link
Member

Choose a reason for hiding this comment

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

And this is an extra empty line. 😆

@liigo
Copy link
Contributor Author

liigo commented Jun 23, 2016

@nikomatsakis Thank you! Done.

@GuillaumeGomez
Copy link
Member

Thanks!

@bors: r+ rollup

@bors
Copy link
Contributor

bors commented Jun 23, 2016

📌 Commit 2d7bac7 has been approved by GuillaumeGomez

@bors
Copy link
Contributor

bors commented Jun 23, 2016

⌛ Testing commit 2d7bac7 with merge a70e068...

@bors
Copy link
Contributor

bors commented Jun 23, 2016

💔 Test failed - auto-mac-64-opt

@alexcrichton
Copy link
Member

@bors: retry

On Thu, Jun 23, 2016 at 4:05 PM, bors [email protected] wrote:

💔 Test failed - auto-mac-64-opt
http://buildbot.rust-lang.org/builders/auto-mac-64-opt/builds/9567


You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
#34379 (comment), or mute
the thread
https://github.com/notifications/unsubscribe/AAD95MtqOcMh8GmOZL14TEtzBsTLFSy5ks5qOxE4gaJpZM4I5dga
.

@bors
Copy link
Contributor

bors commented Jun 25, 2016

⌛ Testing commit 2d7bac7 with merge 7245d2a...

Manishearth added a commit to Manishearth/rust that referenced this pull request Jun 25, 2016
Improve diagnostics E0425: `use` (public) name

E0425: unresolved name
@bors
Copy link
Contributor

bors commented Jun 25, 2016

⛄ The build was interrupted to prioritize another pull request.

bors added a commit that referenced this pull request Jun 25, 2016
Rollup of 8 pull requests

- Successful merges: #34379, #34406, #34411, #34414, #34435, #34438, #34445, #34449
- Failed merges:
GuillaumeGomez added a commit to GuillaumeGomez/rust that referenced this pull request Jun 25, 2016
Improve diagnostics E0425: `use` (public) name

E0425: unresolved name
@bors bors merged commit 2d7bac7 into rust-lang:master Jun 25, 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.

6 participants