Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.
Sign upextern crate privacy is "public" without requiring "pub". #29654
Comments
eddyb
referenced this issue
Nov 6, 2015
Closed
`extern crate` is always treated as `pub` within the crate, but is not visible outside it; `pub extern crate` makes no difference #26775
steveklabnik
added
the
A-lang
label
Nov 7, 2015
This comment has been minimized.
This comment has been minimized.
|
triage: P-high |
rust-highfive
added
the
P-high
label
Nov 12, 2015
nikomatsakis
added
T-lang
and removed
P-high
labels
Nov 12, 2015
nrc
self-assigned this
Nov 12, 2015
This comment has been minimized.
This comment has been minimized.
|
I'm going to close this and discuss further on #26775 - the two issues are very connected and that issue has more discussion.
This is not the case - is_public there is referring to the module itself, not the importing directive, so being true all the time is correct. More on #26775. |
nrc
closed this
Nov 16, 2015
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
eddyb commentedNov 6, 2015
Try on playpen.
This is due to
is_publicbeingtruefor allItemExternCrateregardless of whether they arepub.Even then,
pub extern crateis not handled correctly in all cases, see #26775.