rust/tests/ui/index-help.stderr

error[E0277]: the type `[{integer}]` cannot be indexed by `i32`
  --> $DIR/index-help.rs:3:7
   |
LL |     x[0i32];
   |       ^^^^ slice indices are of type `usize` or ranges of `usize`
   |
   = help: the trait `SliceIndex<[{integer}]>` is not implemented for `i32`
   = help: the trait `SliceIndex<[T]>` is implemented for `usize`
   = note: required for `Vec<{integer}>` to implement `Index<i32>`

error: aborting due to previous error

For more information about this error, try `rustc --explain E0277`.
Make `str` indexing generic on `SliceIndex`. 2019-01-14 07:10:45 -06:00			error[E0277]: the type `[{integer}]` cannot be indexed by `i32`
suggest dereferencing index when trying to use a reference of usize as index 2022-07-24 08:26:44 -05:00			`--> $DIR/index-help.rs:3:7`
Move compile-fail tests with NOTE/HELP annotations to UI 2017-12-10 13:47:55 -06:00			`\|`
Update tests 2019-03-09 06:03:44 -06:00			`LL \| x[0i32];`
suggest dereferencing index when trying to use a reference of usize as index 2022-07-24 08:26:44 -05:00			\| ^^^^ slice indices are of type `usize` or ranges of `usize`
Move compile-fail tests with NOTE/HELP annotations to UI 2017-12-10 13:47:55 -06:00			`\|`
pretty: trim paths of unique symbols If a symbol name can only be imported from one place for a type, and as long as it was not glob-imported anywhere in the current crate, we can trim its printed path and print only the name. This has wide implications on error messages with types, for example, shortening `std::vec::Vec` to just `Vec`, as long as there is no other `Vec` importable anywhere. This adds a new '-Z trim-diagnostic-paths=false' option to control this feature. On the good path, with no diagnosis printed, we should try to avoid issuing this query, so we need to prevent trimmed_def_paths query on several cases. This change also relies on a previous commit that differentiates between `Debug` and `Display` on various rustc types, where the latter is trimmed and presented to the user and the former is not. 2020-09-02 02:40:56 -05:00			= help: the trait `SliceIndex<[{integer}]>` is not implemented for `i32`
Mention implementers of unsatisfied trait When encountering an unsatisfied trait bound, if there are no other suggestions, mention all the types that do implement that trait: ``` error[E0277]: the trait bound `f32: Foo` is not satisfied --> $DIR/impl_wf.rs:22:6 \| LL \| impl Baz<f32> for f32 { } \| ^^^^^^^^ the trait `Foo` is not implemented for `f32` \| = help: the following other types implement trait `Foo`: Option<T> i32 str note: required by a bound in `Baz` --> $DIR/impl_wf.rs:18:31 \| LL \| trait Baz<U: ?Sized> where U: Foo { } \| ^^^ required by this bound in `Baz` ``` Mention implementers of traits in `ImplObligation`s. Do not mention other `impl`s for closures, ranges and `?`. 2021-12-13 14:56:40 -06:00			= help: the trait `SliceIndex<[T]>` is implemented for `usize`
Reword "Required because of the requirements on the impl of ..." 2022-08-15 15:31:37 -05:00			= note: required for `Vec<{integer}>` to implement `Index<i32>`
Move compile-fail tests with NOTE/HELP annotations to UI 2017-12-10 13:47:55 -06:00
			`error: aborting due to previous error`

update tests 2018-03-03 08:59:40 -06:00			For more information about this error, try `rustc --explain E0277`.