Skip to content

Refine privacy error messages to be more accurate #9856

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

Merged
merged 1 commit into from
Oct 19, 2013

Conversation

alexcrichton
Copy link
Member

This stops labeling everything as "is private" when in fact the destination may
be public. Instead, the clause "is inaccessible" is used and the private part of
the flag is called out with a "is private" message.

Closes #9793

This stops labeling everything as "is private" when in fact the destination may
be public. Instead, the clause "is inaccessible" is used and the private part of
the flag is called out with a "is private" message.

Closes rust-lang#9793
@alexcrichton
Copy link
Member Author

I wasn't able to get quite as accurate spans as desired because paths don't have spans on segments, but I think that this gets enough of the point across.

bors added a commit that referenced this pull request Oct 19, 2013
This stops labeling everything as "is private" when in fact the destination may
be public. Instead, the clause "is inaccessible" is used and the private part of
the flag is called out with a "is private" message.

Closes #9793
@bors bors closed this Oct 19, 2013
@bors bors merged commit 082cc96 into rust-lang:master Oct 19, 2013
@alexcrichton alexcrichton deleted the privacy-errors branch October 19, 2013 18:11
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.

use-ing a pub item from a private submodule points to the item as being private
3 participants