rust/tests/ui/cfg/cfgs-on-items.rs

// run-pass
// compile-flags: --cfg fooA --cfg fooB

// fooA AND !bar

#[cfg(all(fooA, not(bar)))]
fn foo1() -> isize { 1 }

// !fooA AND !bar
#[cfg(all(not(fooA), not(bar)))]
fn foo2() -> isize { 2 }

// fooC OR (fooB AND !bar)
#[cfg(any(fooC, all(fooB, not(bar))))]
fn foo2() -> isize { 3 }

// fooA AND bar
#[cfg(all(fooA, bar))]
fn foo3() -> isize { 2 }

// !(fooA AND bar)
#[cfg(not(all(fooA, bar)))]
fn foo3() -> isize { 3 }

pub fn main() {
    assert_eq!(1, foo1());
    assert_eq!(3, foo2());
    assert_eq!(3, foo3());
}
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 07:18:55 -05:00			`// run-pass`
Tests for cfg attribute. 2013-03-19 15:00:10 -05:00			`// compile-flags: --cfg fooA --cfg fooB`

Fix pretty printing for cfg test. 2013-03-19 18:26:23 -05:00			`// fooA AND !bar`
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 15:13:15 -05:00
Continue cfg syntax transition All deprecation warnings have been converted to errors. This includes the warning for multiple cfgs on one item. We'll leave that as an error for some period of time to ensure that all uses are updated before the behavior changes from "or" to "and". 2014-10-11 20:05:54 -05:00			`#[cfg(all(fooA, not(bar)))]`
Mass rename uint/int to usize/isize Now that support has been removed, all lingering use cases are renamed. 2015-03-25 19:06:52 -05:00			`fn foo1() -> isize { 1 }`
Tests for cfg attribute. 2013-03-19 15:00:10 -05:00
Fix pretty printing for cfg test. 2013-03-19 18:26:23 -05:00			`// !fooA AND !bar`
Continue cfg syntax transition All deprecation warnings have been converted to errors. This includes the warning for multiple cfgs on one item. We'll leave that as an error for some period of time to ensure that all uses are updated before the behavior changes from "or" to "and". 2014-10-11 20:05:54 -05:00			`#[cfg(all(not(fooA), not(bar)))]`
Mass rename uint/int to usize/isize Now that support has been removed, all lingering use cases are renamed. 2015-03-25 19:06:52 -05:00			`fn foo2() -> isize { 2 }`
Tests for cfg attribute. 2013-03-19 15:00:10 -05:00
Fix pretty printing for cfg test. 2013-03-19 18:26:23 -05:00			`// fooC OR (fooB AND !bar)`
Continue cfg syntax transition All deprecation warnings have been converted to errors. This includes the warning for multiple cfgs on one item. We'll leave that as an error for some period of time to ensure that all uses are updated before the behavior changes from "or" to "and". 2014-10-11 20:05:54 -05:00			`#[cfg(any(fooC, all(fooB, not(bar))))]`
Mass rename uint/int to usize/isize Now that support has been removed, all lingering use cases are renamed. 2015-03-25 19:06:52 -05:00			`fn foo2() -> isize { 3 }`
Tests for cfg attribute. 2013-03-19 15:00:10 -05:00
rustc: Fix cfg(not(a, b)) to be not(a && b) Previously, the cfg attribute `cfg(not(a, b))` was translated to `(!a && !b)`, but this isn't very useful because that can already be expressed as `cfg(not(a), not(b))`. This commit changes the translation to `!(a && b)` which is more symmetrical of the rest of the `cfg` attribute. Put another way, I would expect `cfg(clause)` to be the opposite of `cfg(not(clause))`, but this is not currently the case with multiple element clauses. 2014-03-14 12:29:13 -05:00			`// fooA AND bar`
Continue cfg syntax transition All deprecation warnings have been converted to errors. This includes the warning for multiple cfgs on one item. We'll leave that as an error for some period of time to ensure that all uses are updated before the behavior changes from "or" to "and". 2014-10-11 20:05:54 -05:00			`#[cfg(all(fooA, bar))]`
Mass rename uint/int to usize/isize Now that support has been removed, all lingering use cases are renamed. 2015-03-25 19:06:52 -05:00			`fn foo3() -> isize { 2 }`
rustc: Fix cfg(not(a, b)) to be not(a && b) Previously, the cfg attribute `cfg(not(a, b))` was translated to `(!a && !b)`, but this isn't very useful because that can already be expressed as `cfg(not(a), not(b))`. This commit changes the translation to `!(a && b)` which is more symmetrical of the rest of the `cfg` attribute. Put another way, I would expect `cfg(clause)` to be the opposite of `cfg(not(clause))`, but this is not currently the case with multiple element clauses. 2014-03-14 12:29:13 -05:00
			`// !(fooA AND bar)`
Continue cfg syntax transition All deprecation warnings have been converted to errors. This includes the warning for multiple cfgs on one item. We'll leave that as an error for some period of time to ensure that all uses are updated before the behavior changes from "or" to "and". 2014-10-11 20:05:54 -05:00			`#[cfg(not(all(fooA, bar)))]`
Mass rename uint/int to usize/isize Now that support has been removed, all lingering use cases are renamed. 2015-03-25 19:06:52 -05:00			`fn foo3() -> isize { 3 }`
Tests for cfg attribute. 2013-03-19 15:00:10 -05:00
test: Make all the run-pass tests use `pub fn main` 2014-01-03 17:30:54 -06:00			`pub fn main() {`
Use assert_eq! rather than assert! where possible 2013-05-18 21:02:45 -05:00			`assert_eq!(1, foo1());`
			`assert_eq!(3, foo2());`
rustc: Fix cfg(not(a, b)) to be not(a && b) Previously, the cfg attribute `cfg(not(a, b))` was translated to `(!a && !b)`, but this isn't very useful because that can already be expressed as `cfg(not(a), not(b))`. This commit changes the translation to `!(a && b)` which is more symmetrical of the rest of the `cfg` attribute. Put another way, I would expect `cfg(clause)` to be the opposite of `cfg(not(clause))`, but this is not currently the case with multiple element clauses. 2014-03-14 12:29:13 -05:00			`assert_eq!(3, foo3());`
Tests for cfg attribute. 2013-03-19 15:00:10 -05:00			`}`