rust/src/test/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 integer literal
}
libsyntax: no binary/hex float literals 2013-02-06 01:49:24 -06: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 01:26:09 -05:00			`0b101010f64;`
Continue evaluating after incorrect float literal 2019-01-11 23:19:44 -06:00			`//~^ ERROR binary float literal is not supported`
libsyntax: no binary/hex float literals 2013-02-06 01:49:24 -06:00			`0b101.010;`
Continue evaluating after incorrect float literal 2019-01-11 23:19:44 -06: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 01:26:09 -05:00			`0b101p4f64;`
syntax: More consistent wording for some literal parsing errors 2019-05-18 14:44:09 -05:00			//~^ ERROR invalid suffix `p4f64` for integer literal
libsyntax: no binary/hex float literals 2013-02-06 01:49:24 -06:00			`}`