rust/tests/ui/indexing/index_message.stderr

error[E0608]: cannot index into a value of type `({integer},)`
  --> $DIR/index_message.rs:3:14
   |
LL |     let _ = z[0];
   |              ^^^ help: to access tuple elements, use: `.0`

error: aborting due to previous error

For more information about this error, try `rustc --explain E0608`.
Tweak tuple indexing suggestion 2023-04-08 16:32:36 -05:00			error[E0608]: cannot index into a value of type `({integer},)`
Improve spans for indexing expressions Indexing is similar to method calls in having an arbitrary left-hand-side and then something on the right, which is the main part of the expression. Method calls already have a span for that right part, but indexing does not. This means that long method chains that use indexing have really bad spans, especially when the indexing panics and that span in coverted into a panic location. This does the same thing as method calls for the AST and HIR, storing an extra span which is then put into the `fn_span` field in THIR. 2023-08-03 14:43:17 -05:00			`--> $DIR/index_message.rs:3:14`
Moved compile-fail tests to ui tests. 2018-08-08 07:28:26 -05:00			`\|`
Update tests 2019-03-09 06:03:44 -06:00			`LL \| let _ = z[0];`
Improve spans for indexing expressions Indexing is similar to method calls in having an arbitrary left-hand-side and then something on the right, which is the main part of the expression. Method calls already have a span for that right part, but indexing does not. This means that long method chains that use indexing have really bad spans, especially when the indexing panics and that span in coverted into a panic location. This does the same thing as method calls for the AST and HIR, storing an extra span which is then put into the `fn_span` field in THIR. 2023-08-03 14:43:17 -05:00			\| ^^^ help: to access tuple elements, use: `.0`
Moved compile-fail tests to ui tests. 2018-08-08 07:28:26 -05:00
			`error: aborting due to previous error`

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