rust/tests/ui/suggestions/suggest-remove-refs-1.stderr

error[E0277]: `&Enumerate<std::slice::Iter<'_, {integer}>>` is not an iterator
  --> $DIR/suggest-remove-refs-1.rs:6:19
   |
LL |     for (i, _) in &v.iter().enumerate() {
   |                   ^^^^^^^^^^^^^^^^^^^^^ `&Enumerate<std::slice::Iter<'_, {integer}>>` is not an iterator
   |
   = help: the trait `Iterator` is not implemented for `&Enumerate<std::slice::Iter<'_, {integer}>>`, which is required by `&Enumerate<std::slice::Iter<'_, {integer}>>: IntoIterator`
   = note: required for `&Enumerate<std::slice::Iter<'_, {integer}>>` to implement `IntoIterator`
help: consider removing the leading `&`-reference
   |
LL -     for (i, _) in &v.iter().enumerate() {
LL +     for (i, _) in v.iter().enumerate() {
   |

error: aborting due to 1 previous error

For more information about this error, try `rustc --explain E0277`.
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			error[E0277]: `&Enumerate<std::slice::Iter<'_, {integer}>>` is not an iterator
Audit uses of `span_suggestion_short` 2020-07-02 00:32:12 -05:00			`--> $DIR/suggest-remove-refs-1.rs:6:19`
Test added. 2018-03-12 21:40:55 -05:00			`\|`
Audit uses of `span_suggestion_short` 2020-07-02 00:32:12 -05:00			`LL \| for (i, _) in &v.iter().enumerate() {`
Make `&`-removal suggestion verbose 2023-01-01 20:43:47 -06:00			\| ^^^^^^^^^^^^^^^^^^^^^ `&Enumerate<std::slice::Iter<'_, {integer}>>` is not an iterator
Test added. 2018-03-12 21:40:55 -05:00			`\|`
Provide more context on derived obligation error primary label Expand the primary span of E0277 when the immediate unmet bound is not what the user wrote: ``` error[E0277]: the trait bound `i32: Bar` is not satisfied --> f100.rs:6:6 \| 6 \| <i32 as Foo>::foo(); \| ^^^ the trait `Bar` is not implemented for `i32`, which is required by `i32: Foo` \| help: this trait has no implementations, consider adding one --> f100.rs:2:1 \| 2 \| trait Bar {} \| ^^^^^^^^^ note: required for `i32` to implement `Foo` --> f100.rs:3:14 \| 3 \| impl<T: Bar> Foo for T {} \| --- ^^^ ^ \| \| \| unsatisfied trait bound introduced here ``` Fix #40120. 2024-01-29 12:31:02 -06:00			= help: the trait `Iterator` is not implemented for `&Enumerate<std::slice::Iter<'_, {integer}>>`, which is required by `&Enumerate<std::slice::Iter<'_, {integer}>>: IntoIterator`
Reword "Required because of the requirements on the impl of ..." 2022-08-15 15:31:37 -05:00			= note: required for `&Enumerate<std::slice::Iter<'_, {integer}>>` to implement `IntoIterator`
Make `&`-removal suggestion verbose 2023-01-01 20:43:47 -06:00			help: consider removing the leading `&`-reference
			`\|`
			`LL - for (i, _) in &v.iter().enumerate() {`
			`LL + for (i, _) in v.iter().enumerate() {`
			`\|`
Test added. 2018-03-12 21:40:55 -05:00
Show number in error message even for one error Co-authored-by: Adrian <adrian.iosdev@gmail.com> 2023-11-21 09:44:16 -06:00			`error: aborting due to 1 previous error`
Test added. 2018-03-12 21:40:55 -05:00
Rebased with master. 2018-03-14 10:49:06 -05:00			For more information about this error, try `rustc --explain E0277`.