nordic-dev.net/rust
nordic-dev.net/rust
2
0
Fork 0
mirror of https://github.com/rust-lang/rust.git synced 2024-12-02 03:33:59 +00:00
Code Issues Packages Projects Releases Wiki Activity
2280d8ea00
rust/tests/ui/parser/float-field.rs

94 lines
4.0 KiB
Rust
Raw Normal View History

parser: Break float tokens into parts in tuple field positions
2020-04-18 18:26:10 +00:00
struct S(u8, (u8, u8));
fn main() {
let s = S(0, (0, 0));
Reformat `float-field.rs` test. - Put every literal in its own braces, rather than just some of them, for maximal error recovery. - Add a blank line between every case, for readability.
2024-02-28 05:29:41 +00:00
{ s.1e1; } //~ ERROR no field `1e1` on type `S`
{ s.1.; } //~ ERROR unexpected token: `;`
{ s.1.1; }
{ s.1.1e1; } //~ ERROR no field `1e1` on type `(u8, u8)`
parser: Break float tokens into parts in tuple field positions
2020-04-18 18:26:10 +00:00
{ s.1e+; } //~ ERROR unexpected token: `1e+`
//~| ERROR expected one of `.`, `;`, `?`, `}`, or an operator, found `1e+`
//~| ERROR expected at least one digit in exponent
Reformat `float-field.rs` test. - Put every literal in its own braces, rather than just some of them, for maximal error recovery. - Add a blank line between every case, for readability.
2024-02-28 05:29:41 +00:00
parser: Break float tokens into parts in tuple field positions
2020-04-18 18:26:10 +00:00
{ s.1e-; } //~ ERROR unexpected token: `1e-`
//~| ERROR expected one of `.`, `;`, `?`, `}`, or an operator, found `1e-`
//~| ERROR expected at least one digit in exponent
Reformat `float-field.rs` test. - Put every literal in its own braces, rather than just some of them, for maximal error recovery. - Add a blank line between every case, for readability.
2024-02-28 05:29:41 +00:00
parser: Break float tokens into parts in tuple field positions
2020-04-18 18:26:10 +00:00
{ s.1e+1; } //~ ERROR unexpected token: `1e+1`
//~| ERROR expected one of `.`, `;`, `?`, `}`, or an operator, found `1e+1`
Reformat `float-field.rs` test. - Put every literal in its own braces, rather than just some of them, for maximal error recovery. - Add a blank line between every case, for readability.
2024-02-28 05:29:41 +00:00
parser: Break float tokens into parts in tuple field positions
2020-04-18 18:26:10 +00:00
{ s.1e-1; } //~ ERROR unexpected token: `1e-1`
//~| ERROR expected one of `.`, `;`, `?`, `}`, or an operator, found `1e-1`
Reformat `float-field.rs` test. - Put every literal in its own braces, rather than just some of them, for maximal error recovery. - Add a blank line between every case, for readability.
2024-02-28 05:29:41 +00:00
parser: Break float tokens into parts in tuple field positions
2020-04-18 18:26:10 +00:00
{ s.1.1e+1; } //~ ERROR unexpected token: `1.1e+1`
//~| ERROR expected one of `.`, `;`, `?`, `}`, or an operator, found `1.1e+1`
Reformat `float-field.rs` test. - Put every literal in its own braces, rather than just some of them, for maximal error recovery. - Add a blank line between every case, for readability.
2024-02-28 05:29:41 +00:00
parser: Break float tokens into parts in tuple field positions
2020-04-18 18:26:10 +00:00
{ s.1.1e-1; } //~ ERROR unexpected token: `1.1e-1`
//~| ERROR expected one of `.`, `;`, `?`, `}`, or an operator, found `1.1e-1`
Reformat `float-field.rs` test. - Put every literal in its own braces, rather than just some of them, for maximal error recovery. - Add a blank line between every case, for readability.
2024-02-28 05:29:41 +00:00
{ s.0x1e1; } //~ ERROR no field `0x1e1` on type `S`
Use `LitKind::Err` for floats with unsupported bases. This slightly changes error messages in `float-field.rs`, but nothing of real importance.
2024-02-28 05:30:20 +00:00
{ s.0x1.; } //~ ERROR hexadecimal float literal is not supported
//~| ERROR unexpected token: `0x1.`
//~| ERROR expected one of `.`, `;`, `?`, `}`, or an operator, found `0x1.`
Reformat `float-field.rs` test. - Put every literal in its own braces, rather than just some of them, for maximal error recovery. - Add a blank line between every case, for readability.
2024-02-28 05:29:41 +00:00
Use `LitKind::Err` for floats with unsupported bases. This slightly changes error messages in `float-field.rs`, but nothing of real importance.
2024-02-28 05:30:20 +00:00
{ s.0x1.1; } //~ ERROR hexadecimal float literal is not supported
//~| ERROR unexpected token: `0x1.1`
//~| expected one of `.`, `;`, `?`, `}`, or an operator, found `0x1.1`
Reformat `float-field.rs` test. - Put every literal in its own braces, rather than just some of them, for maximal error recovery. - Add a blank line between every case, for readability.
2024-02-28 05:29:41 +00:00
Use `LitKind::Err` for floats with unsupported bases. This slightly changes error messages in `float-field.rs`, but nothing of real importance.
2024-02-28 05:30:20 +00:00
{ s.0x1.1e1; } //~ ERROR hexadecimal float literal is not supported
//~| ERROR unexpected token: `0x1.1e1`
//~| expected one of `.`, `;`, `?`, `}`, or an operator, found `0x1.1e1`
Reformat `float-field.rs` test. - Put every literal in its own braces, rather than just some of them, for maximal error recovery. - Add a blank line between every case, for readability.
2024-02-28 05:29:41 +00:00
parser: Break float tokens into parts in tuple field positions
2020-04-18 18:26:10 +00:00
{ s.0x1e+; } //~ ERROR expected expression, found `;`
Reformat `float-field.rs` test. - Put every literal in its own braces, rather than just some of them, for maximal error recovery. - Add a blank line between every case, for readability.
2024-02-28 05:29:41 +00:00
parser: Break float tokens into parts in tuple field positions
2020-04-18 18:26:10 +00:00
{ s.0x1e-; } //~ ERROR expected expression, found `;`
Reformat `float-field.rs` test. - Put every literal in its own braces, rather than just some of them, for maximal error recovery. - Add a blank line between every case, for readability.
2024-02-28 05:29:41 +00:00
{ s.0x1e+1; } //~ ERROR no field `0x1e` on type `S`
{ s.0x1e-1; } //~ ERROR no field `0x1e` on type `S`
parser: Break float tokens into parts in tuple field positions
2020-04-18 18:26:10 +00:00
{ s.0x1.1e+1; } //~ ERROR unexpected token: `0x1.1e+1`
//~| ERROR expected one of `.`, `;`, `?`, `}`, or an operator, found `0x1.1e+1`
//~| ERROR hexadecimal float literal is not supported
Reformat `float-field.rs` test. - Put every literal in its own braces, rather than just some of them, for maximal error recovery. - Add a blank line between every case, for readability.
2024-02-28 05:29:41 +00:00
parser: Break float tokens into parts in tuple field positions
2020-04-18 18:26:10 +00:00
{ s.0x1.1e-1; } //~ ERROR unexpected token: `0x1.1e-1`
//~| ERROR expected one of `.`, `;`, `?`, `}`, or an operator, found `0x1.1e-1`
//~| ERROR hexadecimal float literal is not supported
Reformat `float-field.rs` test. - Put every literal in its own braces, rather than just some of them, for maximal error recovery. - Add a blank line between every case, for readability.
2024-02-28 05:29:41 +00:00
{ s.1e1f32; } //~ ERROR no field `1e1` on type `S`
//~| ERROR suffixes on a tuple index are invalid
{ s.1.f32; } //~ ERROR no field `f32` on type `(u8, u8)`
{ s.1.1f32; } //~ ERROR suffixes on a tuple index are invalid
{ s.1.1e1f32; } //~ ERROR no field `1e1` on type `(u8, u8)`
//~| ERROR suffixes on a tuple index are invalid
parser: Break float tokens into parts in tuple field positions
2020-04-18 18:26:10 +00:00
{ s.1e+f32; } //~ ERROR unexpected token: `1e+f32`
//~| ERROR expected one of `.`, `;`, `?`, `}`, or an operator, found `1e+f32`
//~| ERROR expected at least one digit in exponent
Reformat `float-field.rs` test. - Put every literal in its own braces, rather than just some of them, for maximal error recovery. - Add a blank line between every case, for readability.
2024-02-28 05:29:41 +00:00
parser: Break float tokens into parts in tuple field positions
2020-04-18 18:26:10 +00:00
{ s.1e-f32; } //~ ERROR unexpected token: `1e-f32`
//~| ERROR expected one of `.`, `;`, `?`, `}`, or an operator, found `1e-f32`
//~| ERROR expected at least one digit in exponent
Reformat `float-field.rs` test. - Put every literal in its own braces, rather than just some of them, for maximal error recovery. - Add a blank line between every case, for readability.
2024-02-28 05:29:41 +00:00
parser: Break float tokens into parts in tuple field positions
2020-04-18 18:26:10 +00:00
{ s.1e+1f32; } //~ ERROR unexpected token: `1e+1f32`
//~| ERROR expected one of `.`, `;`, `?`, `}`, or an operator, found `1e+1f32`
Reformat `float-field.rs` test. - Put every literal in its own braces, rather than just some of them, for maximal error recovery. - Add a blank line between every case, for readability.
2024-02-28 05:29:41 +00:00
parser: Break float tokens into parts in tuple field positions
2020-04-18 18:26:10 +00:00
{ s.1e-1f32; } //~ ERROR unexpected token: `1e-1f32`
//~| ERROR expected one of `.`, `;`, `?`, `}`, or an operator, found `1e-1f32`
Reformat `float-field.rs` test. - Put every literal in its own braces, rather than just some of them, for maximal error recovery. - Add a blank line between every case, for readability.
2024-02-28 05:29:41 +00:00
parser: Break float tokens into parts in tuple field positions
2020-04-18 18:26:10 +00:00
{ s.1.1e+1f32; } //~ ERROR unexpected token: `1.1e+1f32`
//~| ERROR expected one of `.`, `;`, `?`, `}`, or an operator, found `1.1e+1f32`
Reformat `float-field.rs` test. - Put every literal in its own braces, rather than just some of them, for maximal error recovery. - Add a blank line between every case, for readability.
2024-02-28 05:29:41 +00:00
parser: Break float tokens into parts in tuple field positions
2020-04-18 18:26:10 +00:00
{ s.1.1e-1f32; } //~ ERROR unexpected token: `1.1e-1f32`
//~| ERROR expected one of `.`, `;`, `?`, `}`, or an operator, found `1.1e-1f32`
}
Reference in New Issue Copy Permalink