granite-rust/src/test/ui/xc-private-method.rs

// aux-build:xc_private_method_lib.rs

extern crate xc_private_method_lib;

fn main() {
    let _ = xc_private_method_lib::Struct::static_meth_struct();
    //~^ ERROR: method `static_meth_struct` is private

    let _ = xc_private_method_lib::Enum::static_meth_enum();
    //~^ ERROR: method `static_meth_enum` is private
}
librustc: Forbid access to cross-crate private static methods 2013-03-20 14:38:57 -07:00			`// aux-build:xc_private_method_lib.rs`

extern mod => extern crate This was previously implemented, and it just needed a snapshot to go through 2014-02-14 10:10:06 -08:00			`extern crate xc_private_method_lib;`
librustc: Forbid access to cross-crate private static methods 2013-03-20 14:38:57 -07:00
			`fn main() {`
Correctly encode item visibility in metadata This fixes private statics and functions from being usable cross-crates, along with some bad privacy error messages. This is a reopening of #8365 with all the privacy checks in privacy.rs instead of resolve.rs (where they should be anyway). These maps of exported items will hopefully get used for generating documentation by rustdoc Closes #8592 2013-08-07 00:11:34 -07:00			`let _ = xc_private_method_lib::Struct::static_meth_struct();`
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			//~^ ERROR: method `static_meth_struct` is private
Enable privacy check for enum methods. 2013-08-07 14:29:29 +02:00
Correctly encode item visibility in metadata This fixes private statics and functions from being usable cross-crates, along with some bad privacy error messages. This is a reopening of #8365 with all the privacy checks in privacy.rs instead of resolve.rs (where they should be anyway). These maps of exported items will hopefully get used for generating documentation by rustdoc Closes #8592 2013-08-07 00:11:34 -07:00			`let _ = xc_private_method_lib::Enum::static_meth_enum();`
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			//~^ ERROR: method `static_meth_enum` is private
librustc: Forbid access to cross-crate private static methods 2013-03-20 14:38:57 -07:00			`}`