rust/tests/ui/tuple/tuple-index-out-of-bounds.stderr

error[E0609]: no field `2` on type `Point`
  --> $DIR/tuple-index-out-of-bounds.rs:7:12
   |
LL |     origin.2;
   |            ^ unknown field
   |
   = note: available fields are: `0`, `1`

error[E0609]: no field `2` on type `({integer}, {integer})`
  --> $DIR/tuple-index-out-of-bounds.rs:12:11
   |
LL |     tuple.2;
   |           ^ unknown field
   |
   = note: available fields are: `0`, `1`

error: aborting due to 2 previous errors

For more information about this error, try `rustc --explain E0609`.
Moved compile-fail tests to ui tests. 2018-08-08 14:28:26 +02:00			error[E0609]: no field `2` on type `Point`
Remove licenses 2018-12-25 08:56:47 -07:00			`--> $DIR/tuple-index-out-of-bounds.rs:7:12`
Moved compile-fail tests to ui tests. 2018-08-08 14:28:26 +02:00			`\|`
			`LL \| origin.2;`
recover primary span label 2023-11-09 06:01:10 +00:00			`\| ^ unknown field`
Suggest `unwrap()` on field not found for `Result`/`Option` When encountering a `Result<T, _>` or `Option<T>` where `T` has a field that's being accessed, suggest calling `.unwrap()` to get to the field. 2023-10-24 23:31:47 +00:00			`\|`
Do not provide field typo suggestions for tuples and tuple structs 2025-07-30 16:21:40 +00:00			= note: available fields are: `0`, `1`
Moved compile-fail tests to ui tests. 2018-08-08 14:28:26 +02:00
			error[E0609]: no field `2` on type `({integer}, {integer})`
Remove licenses 2018-12-25 08:56:47 -07:00			`--> $DIR/tuple-index-out-of-bounds.rs:12:11`
Moved compile-fail tests to ui tests. 2018-08-08 14:28:26 +02:00			`\|`
			`LL \| tuple.2;`
recover primary span label 2023-11-09 06:01:10 +00:00			`\| ^ unknown field`
Account for bare tuples in field searching logic When looking for the field names and types of a given type, account for tuples. This allows suggestions for incorrectly nested field accesses and field name typos to trigger as intended. Previously these suggestions only worked on `ty::Adt`, including tuple structs which are no different to tuples, so they should behave the same in suggestions. ``` error[E0599]: no method named `get_ref` found for tuple `(BufReader<File>,)` in the current scope --> $DIR/missing-field-access.rs:11:15 \| LL \| let x = f.get_ref(); \| ^^^^^^^ method not found in `(BufReader<File>,)` \| help: one of the expressions' fields has a method of the same name \| LL \| let x = f.0.get_ref(); \| ++ ``` 2025-07-29 18:39:16 +00:00			`\|`
Do not provide field typo suggestions for tuples and tuple structs 2025-07-30 16:21:40 +00:00			= note: available fields are: `0`, `1`
Moved compile-fail tests to ui tests. 2018-08-08 14:28:26 +02:00
			`error: aborting due to 2 previous errors`

			For more information about this error, try `rustc --explain E0609`.