rust/tests/ui/numbers-arithmetic/floatlits.rs

//@ run-pass


pub fn main() {
    let f = 4.999999999999f64;
    assert!(f > 4.90f64);
    assert!(f < 5.0f64);
    let g = 4.90000000001e-10f64;
    assert!(g > 5e-11f64);
    assert!(g < 5e-9f64);
}
[AUTO-GENERATED] Migrate ui tests from `//` to `//@` directives 2024-02-16 20:02:50 +00:00			`//@ run-pass`
Reformat source tree (minus a couple tests that are still grumpy). 2011-06-15 11:19:50 -07:00

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
check-fast fallout from removing export, r=burningtree 2013-02-01 19:43:17 -08:00			`pub fn main() {`
librustc: Remove the fallback to `int` for integers and `f64` for floating point numbers for real. This will break code that looks like: let mut x = 0; while ... { x += 1; } println!("{}", x); Change that code to: let mut x = 0i; while ... { x += 1; } println!("{}", x); Closes #15201. [breaking-change] 2014-06-27 12:30:25 -07:00			`let f = 4.999999999999f64;`
Remove some unnecessary parens in `assert!` conditions While working on #122661, some of these started triggering our "unnecessary parens" lints due to a change in the `assert!` desugaring. A cursory search identified a few more. Some of these have been carried from before 1.0, were a bulk rename from the previous name of `assert!` left them in that state. I went and removed as many of these unnecessary parens as possible in order to have fewer annoyances in the future if we make the lint smarter. 2025-01-23 18:40:41 +00:00			`assert!(f > 4.90f64);`
			`assert!(f < 5.0f64);`
librustc: Remove the fallback to `int` for integers and `f64` for floating point numbers for real. This will break code that looks like: let mut x = 0; while ... { x += 1; } println!("{}", x); Change that code to: let mut x = 0i; while ... { x += 1; } println!("{}", x); Closes #15201. [breaking-change] 2014-06-27 12:30:25 -07:00			`let g = 4.90000000001e-10f64;`
Remove some unnecessary parens in `assert!` conditions While working on #122661, some of these started triggering our "unnecessary parens" lints due to a change in the `assert!` desugaring. A cursory search identified a few more. Some of these have been carried from before 1.0, were a bulk rename from the previous name of `assert!` left them in that state. I went and removed as many of these unnecessary parens as possible in order to have fewer annoyances in the future if we make the lint smarter. 2025-01-23 18:40:41 +00:00			`assert!(g > 5e-11f64);`
			`assert!(g < 5e-9f64);`
Reformat This changes the indexing syntax from .() to [], the vector syntax from ~[] to [] and the extension syntax from #fmt() to #fmt[] 2011-08-19 15:16:48 -07:00			`}`