rust/tests/ui/parser/no-binary-float-literal.rs

fn main() {
    0b101010f64;
    //~^ ERROR binary float literal is not supported
    0b101.010;
    //~^ ERROR binary float literal is not supported
    0b101p4f64;
    //~^ ERROR invalid suffix `p4f64` for number literal
}
libsyntax: no binary/hex float literals 2013-02-06 07:49:24 +00:00			`fn main() {`
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 06:26:09 +00:00			`0b101010f64;`
Continue evaluating after incorrect float literal 2019-01-12 05:19:44 +00:00			`//~^ ERROR binary float literal is not supported`
libsyntax: no binary/hex float literals 2013-02-06 07:49:24 +00:00			`0b101.010;`
Continue evaluating after incorrect float literal 2019-01-12 05:19:44 +00:00			`//~^ ERROR binary float literal is not supported`
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 06:26:09 +00:00			`0b101p4f64;`
Update error to reflect that integer literals can have float suffixes For example, `1` is parsed as an integer literal, but it can be turned into a float with the suffix `f32`. Now the error calls them "numeric literals" and notes that you can add a float suffix since they can be either integers or floats. 2020-11-22 22:29:46 +00:00			//~^ ERROR invalid suffix `p4f64` for number literal
libsyntax: no binary/hex float literals 2013-02-06 07:49:24 +00:00			`}`