rust/tests/ui/issues/issue-3993.rs

use zoo::fly; //~ ERROR: function `fly` is private

mod zoo {
    fn fly() {}
}


fn main() {
    fly();
}
Fix existing privacy/visibility violations This commit fixes all of the fallout of the previous commit which is an attempt to refine privacy. There were a few unfortunate leaks which now must be plugged, and the most horrible one is the current `shouldnt_be_public` module now inside `std::rt`. I think that this either needs a slight reorganization of the runtime, or otherwise it needs to just wait for the external users of these modules to get replaced with their `rt` implementations. Other fixes involve making things pub which should be pub, and otherwise updating error messages that now reference privacy instead of referencing an "unresolved name" (yay!). 2013-10-05 14:44:37 -07:00			use zoo::fly; //~ ERROR: function `fly` is private
Disallow importing private items resolve wasn't checking that a `use` referred to a public item. r=brson 2012-11-29 12:08:40 -08:00
			`mod zoo {`
Fix fallout 2013-08-07 23:20:06 -04:00			`fn fly() {}`
Disallow importing private items resolve wasn't checking that a `use` referred to a public item. r=brson 2012-11-29 12:08:40 -08:00			`}`


Fix existing privacy/visibility violations This commit fixes all of the fallout of the previous commit which is an attempt to refine privacy. There were a few unfortunate leaks which now must be plugged, and the most horrible one is the current `shouldnt_be_public` module now inside `std::rt`. I think that this either needs a slight reorganization of the runtime, or otherwise it needs to just wait for the external users of these modules to get replaced with their `rt` implementations. Other fixes involve making things pub which should be pub, and otherwise updating error messages that now reference privacy instead of referencing an "unresolved name" (yay!). 2013-10-05 14:44:37 -07:00			`fn main() {`
			`fly();`
			`}`