rust/tests/ui/consts/auxiliary/issue-17718-aux.rs

use std::sync::atomic;

pub const C1: usize = 1;
pub const C2: atomic::AtomicUsize = atomic::AtomicUsize::new(0);
pub const C3: fn() = { fn foo() {} foo };
pub const C4: usize = C1 * C1 + C1 / C1;
pub const C5: &'static usize = &C4;

pub static S1: usize = 3;
pub static S2: atomic::AtomicUsize = atomic::AtomicUsize::new(0);
move auxiliary builds to a test-relative `aux` Instead of finding aux-build files in `auxiliary`, we now search for an `aux` directory relative to the test. So if your test is `compile-fail/foo.rs`, we would look in `compile-fail/aux`. Similarly, we ignore the `aux` directory when searching for tets. 2016-04-26 12:51:14 -05:00			`use std::sync::atomic;`

			`pub const C1: usize = 1;`
			`pub const C2: atomic::AtomicUsize = atomic::AtomicUsize::new(0);`
rustc: don't recurse through nested items in decoded HIR fragments. 2016-09-17 11:06:21 -05:00			`pub const C3: fn() = { fn foo() {} foo };`
move auxiliary builds to a test-relative `aux` Instead of finding aux-build files in `auxiliary`, we now search for an `aux` directory relative to the test. So if your test is `compile-fail/foo.rs`, we would look in `compile-fail/aux`. Similarly, we ignore the `aux` directory when searching for tets. 2016-04-26 12:51:14 -05:00			`pub const C4: usize = C1 * C1 + C1 / C1;`
			`pub const C5: &'static usize = &C4;`

			`pub static S1: usize = 3;`
			`pub static S2: atomic::AtomicUsize = atomic::AtomicUsize::new(0);`