os-rust/tests/ui/cfg/cfg-in-crate-1.rs

//@ run-pass
//@ compile-flags: --cfg bar --check-cfg=cfg(bar) -D warnings

#![cfg(bar)]

fn main() {}
Add `// run-pass` annotations to all the tests under `ui/run-pass/`. (I may have accidentally added it to some auxilliary crates as well; my emacs-macro-based methodology was pretty crude.) 2018-08-30 14:18:55 +02:00			`//@ run-pass`
compiletest: add enable-by-default check-cfg 2024-04-07 00:33:37 +02:00			`//@ compile-flags: --cfg bar --check-cfg=cfg(bar) -D warnings`

rustc: Process #[cfg]/#[cfg_attr] on crates This commit implements processing these two attributes at the crate level as well as at the item level. When #[cfg] is applied at the crate level, then the entire crate will be omitted if the cfg doesn't match. The #[cfg_attr] attribute is processed as usual in that the attribute is included or not depending on whether the cfg matches. This was spurred on by motivations of #18585 where #[cfg_attr] annotations will be applied at the crate-level. cc #18585 2014-11-04 14:59:42 -08:00			`#![cfg(bar)]`

			`fn main() {}`