rust/tests/ui/privacy/privacy-reexport.rs

//@ run-pass
//@ aux-build:privacy_reexport.rs


extern crate privacy_reexport;

pub fn main() {
    // Check that public extern crates are visible to outside crates
    privacy_reexport::core::cell::Cell::new(0);

    privacy_reexport::bar::frob();
}
[AUTO-GENERATED] Migrate ui tests from `//` to `//@` directives 2024-02-16 20:02:50 +00:00			`//@ run-pass`
			`//@ aux-build:privacy_reexport.rs`
Move more of the exportation burden into privacy I added a test case which does not compile today, and required changes on privacy's side of things to get right. Additionally, this moves a good bit of logic which did not belong in reachability into privacy. All of reachability should solely be responsible for determining what the reachable surface area of a crate is given the exported surface area (where the exported surface area is that which is usable by external crates). Privacy will now correctly figure out what's exported by deeply looking through reexports. Previously if a module were reexported under another name, nothing in the module would actually get exported in the executable. I also consolidated the phases of privacy to be clearer about what's an input to what. The privacy checking pass no longer uses the notion of an "all public" path, and the embargo visitor is no longer an input to the checking pass. Currently the embargo visitor is built as a saturating analysis because it's unknown what portions of the AST are going to get re-exported. 2013-11-20 15:15:34 -08:00
rustdoc: Replace no-pretty-expanded with pretty-expanded Now that features must be declared expanded source often does not compile. This adds 'pretty-expanded' to a bunch of test cases that still work. 2015-03-22 13:13:15 -07:00
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 privacy_reexport;`
Move more of the exportation burden into privacy I added a test case which does not compile today, and required changes on privacy's side of things to get right. Additionally, this moves a good bit of logic which did not belong in reachability into privacy. All of reachability should solely be responsible for determining what the reachable surface area of a crate is given the exported surface area (where the exported surface area is that which is usable by external crates). Privacy will now correctly figure out what's exported by deeply looking through reexports. Previously if a module were reexported under another name, nothing in the module would actually get exported in the executable. I also consolidated the phases of privacy to be clearer about what's an input to what. The privacy checking pass no longer uses the notion of an "all public" path, and the embargo visitor is no longer an input to the checking pass. Currently the embargo visitor is built as a saturating analysis because it's unknown what portions of the AST are going to get re-exported. 2013-11-20 15:15:34 -08:00
test: Make all the run-pass tests use `pub fn main` 2014-01-03 15:30:54 -08:00			`pub fn main() {`
Fix the visibility of extern crate declarations and stop warning on pub extern crate 2016-02-02 20:21:24 +00:00			`// Check that public extern crates are visible to outside crates`
			`privacy_reexport::core::cell::Cell::new(0);`

Move more of the exportation burden into privacy I added a test case which does not compile today, and required changes on privacy's side of things to get right. Additionally, this moves a good bit of logic which did not belong in reachability into privacy. All of reachability should solely be responsible for determining what the reachable surface area of a crate is given the exported surface area (where the exported surface area is that which is usable by external crates). Privacy will now correctly figure out what's exported by deeply looking through reexports. Previously if a module were reexported under another name, nothing in the module would actually get exported in the executable. I also consolidated the phases of privacy to be clearer about what's an input to what. The privacy checking pass no longer uses the notion of an "all public" path, and the embargo visitor is no longer an input to the checking pass. Currently the embargo visitor is built as a saturating analysis because it's unknown what portions of the AST are going to get re-exported. 2013-11-20 15:15:34 -08:00			`privacy_reexport::bar::frob();`
			`}`