rust/tests/run-make/extern-flag-disambiguates/d.rs

#[cfg(before)]
extern crate a;
#[cfg(after)]
extern crate a;
extern crate b;
extern crate c;

fn t(a: &'static usize) -> usize {
    a as *const _ as usize
}

fn main() {
    assert_eq!(t(a::token()), t(b::a_token()));
    assert!(t(a::token()) != t(c::a_token()));
}
Run rustfmt on `tests/run-make/`. With the exception of `tests/run-make/translation/test.rs`, which has a syntax error. The expected output in `rustdoc-error-lines/rmake.rs`'s required slight tweaking. The two `reproducible-build.rs` files need `// ignore-tidy-linelength` because rustfmt produces lines longer than 100 chars, which tidy doesn't like, yuk. 2024-05-29 00:01:33 -05:00			`#[cfg(before)]`
			`extern crate a;`
			`#[cfg(after)]`
			`extern crate a;`
rustc: Add a flag for specifying dependencies This comit implements a new flag, --extern, which is used to specify where a crate is located. The purpose of this flag is to bypass the normal crate loading/matching of the compiler to point it directly at the right file. This flag takes the form `--extern foo=bar` where `foo` is the name of a crate and `bar` is the location at which to find the crate. Multiple `--extern` directives are allowed with the same crate name to specify the rlib/dylib pair for a crate. It is invalid to specify more than one rlib or more than one dylib, and it's required that the crates are valid rust crates. I have also added some extensive documentation to metadata::loader about how crate loading should work. RFC: 0035-remove-crate-id 2014-07-01 10:37:54 -05:00			`extern crate b;`
			`extern crate c;`

Run rustfmt on `tests/run-make/`. With the exception of `tests/run-make/translation/test.rs`, which has a syntax error. The expected output in `rustdoc-error-lines/rmake.rs`'s required slight tweaking. The two `reproducible-build.rs` files need `// ignore-tidy-linelength` because rustfmt produces lines longer than 100 chars, which tidy doesn't like, yuk. 2024-05-29 00:01:33 -05:00			`fn t(a: &'static usize) -> usize {`
			`a as *const _ as usize`
			`}`
rustc: Add a flag for specifying dependencies This comit implements a new flag, --extern, which is used to specify where a crate is located. The purpose of this flag is to bypass the normal crate loading/matching of the compiler to point it directly at the right file. This flag takes the form `--extern foo=bar` where `foo` is the name of a crate and `bar` is the location at which to find the crate. Multiple `--extern` directives are allowed with the same crate name to specify the rlib/dylib pair for a crate. It is invalid to specify more than one rlib or more than one dylib, and it's required that the crates are valid rust crates. I have also added some extensive documentation to metadata::loader about how crate loading should work. RFC: 0035-remove-crate-id 2014-07-01 10:37:54 -05:00
			`fn main() {`
Use `assert_eq!` instead of `assert!` in tests 2015-06-07 13:00:38 -05:00			`assert_eq!(t(a::token()), t(b::a_token()));`
rustc: Add a flag for specifying dependencies This comit implements a new flag, --extern, which is used to specify where a crate is located. The purpose of this flag is to bypass the normal crate loading/matching of the compiler to point it directly at the right file. This flag takes the form `--extern foo=bar` where `foo` is the name of a crate and `bar` is the location at which to find the crate. Multiple `--extern` directives are allowed with the same crate name to specify the rlib/dylib pair for a crate. It is invalid to specify more than one rlib or more than one dylib, and it's required that the crates are valid rust crates. I have also added some extensive documentation to metadata::loader about how crate loading should work. RFC: 0035-remove-crate-id 2014-07-01 10:37:54 -05:00			`assert!(t(a::token()) != t(c::a_token()));`
			`}`