rust/tests/ui/consts/const-contents.rs

// run-pass
// Issue #570
#![allow(non_upper_case_globals)]

static lsl : isize = 1 << 2;
static add : isize = 1 + 2;
static addf : f64 = 1.0 + 2.0;
static not : isize = !0;
static notb : bool = !true;
static neg : isize = -(1);

pub fn main() {
    assert_eq!(lsl, 4);
    assert_eq!(add, 3);
    assert_eq!(addf, 3.0);
    assert_eq!(not, -1);
    assert_eq!(notb, false);
    assert_eq!(neg, -1);
}
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`
Add test with implemented bits of issue #570. 2011-11-09 01:44:42 -08:00			`// Issue #570`
Add `#![allow(..)]` for a slew of lints of migrated run-pass tests, to silence stderr output. 2018-08-31 15:02:01 +02:00			`#![allow(non_upper_case_globals)]`
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
Mass rename uint/int to usize/isize Now that support has been removed, all lingering use cases are renamed. 2015-03-25 17:06:52 -07:00			`static lsl : isize = 1 << 2;`
			`static add : isize = 1 + 2;`
remove the `float` type It is simply defined as `f64` across every platform right now. A use case hasn't been presented for a `float` type defined as the highest precision floating point type implemented in hardware on the platform. Performance-wise, using the smallest precision correct for the use case greatly saves on cache space and allows for fitting more numbers into SSE/AVX registers. If there was a use case, this could be implemented as simply a type alias or a struct thanks to `#[cfg(...)]`. Closes #6592 The mailing list thread, for reference: https://mail.mozilla.org/pipermail/rust-dev/2013-July/004632.html 2013-09-26 02:26:09 -04:00			`static addf : f64 = 1.0 + 2.0;`
Mass rename uint/int to usize/isize Now that support has been removed, all lingering use cases are renamed. 2015-03-25 17:06:52 -07:00			`static not : isize = !0;`
librustc: Remove the `const` declaration form everywhere 2013-03-22 14:00:15 -07:00			`static notb : bool = !true;`
Mass rename uint/int to usize/isize Now that support has been removed, all lingering use cases are renamed. 2015-03-25 17:06:52 -07:00			`static neg : isize = -(1);`
Add test with implemented bits of issue #570. 2011-11-09 01:44:42 -08:00
check-fast fallout from removing export, r=burningtree 2013-02-01 19:43:17 -08:00			`pub fn main() {`
Use assert_eq! rather than assert! where possible 2013-05-18 22:02:45 -04:00			`assert_eq!(lsl, 4);`
			`assert_eq!(add, 3);`
remove the `float` type It is simply defined as `f64` across every platform right now. A use case hasn't been presented for a `float` type defined as the highest precision floating point type implemented in hardware on the platform. Performance-wise, using the smallest precision correct for the use case greatly saves on cache space and allows for fitting more numbers into SSE/AVX registers. If there was a use case, this could be implemented as simply a type alias or a struct thanks to `#[cfg(...)]`. Closes #6592 The mailing list thread, for reference: https://mail.mozilla.org/pipermail/rust-dev/2013-July/004632.html 2013-09-26 02:26:09 -04:00			`assert_eq!(addf, 3.0);`
Use assert_eq! rather than assert! where possible 2013-05-18 22:02:45 -04:00			`assert_eq!(not, -1);`
			`assert_eq!(notb, false);`
			`assert_eq!(neg, -1);`
Add test with implemented bits of issue #570. 2011-11-09 01:44:42 -08:00			`}`