rust/tests/ui/for/for-c-in-str.stderr

error[E0277]: `&str` is not an iterator
  --> $DIR/for-c-in-str.rs:4:14
   |
LL |     for c in "asdf" {
   |              ^^^^^^ `&str` is not an iterator; try calling `.chars()` or `.bytes()`
   |
   = help: the trait `Iterator` is not implemented for `&str`, which is required by `&str: IntoIterator`
   = note: required for `&str` to implement `IntoIterator`

error: aborting due to 1 previous error

For more information about this error, try `rustc --explain E0277`.
Reword `rustc_on_unimplemented` errors for `Iterator` - Detect one element array of `Range` type, which is potentially a typo: `for _ in [0..10] {}` where iterating between `0` and `10` was intended. (#23141) - Suggest `.bytes()` and `.chars()` for `String`. - Suggest borrowing or `.iter()` on arrays (#36391) - Suggest using range literal when iterating on integers (#34353) - Do not suggest `.iter()` by default (#50773, #46806) 2018-10-10 01:53:53 +00:00			error[E0277]: `&str` is not an iterator
Fix tests from rebase 2020-09-07 09:01:45 +00:00			`--> $DIR/for-c-in-str.rs:4:14`
For E0277 on `for` loops, point at first line When E0277's span points at a `for` loop, the actual issue is in the element being iterated. Instead of pointing at the entire loop, point only at the first line (when possible) so that the span ends in the element for which E0277 was triggered. 2018-01-23 22:58:39 +00:00			`\|`
Update UI tests 2018-02-23 00:42:32 +00:00			`LL \| for c in "asdf" {`
Fix test after rebase 2018-02-01 22:16:53 +00:00			\| ^^^^^^ `&str` is not an iterator; try calling `.chars()` or `.bytes()`
For E0277 on `for` loops, point at first line When E0277's span points at a `for` loop, the actual issue is in the element being iterated. Instead of pointing at the entire loop, point only at the first line (when possible) so that the span ends in the element for which E0277 was triggered. 2018-01-23 22:58:39 +00: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 18:31:02 +00:00			= help: the trait `Iterator` is not implemented for `&str`, which is required by `&str: IntoIterator`
Reword "Required because of the requirements on the impl of ..." 2022-08-15 20:31:37 +00:00			= note: required for `&str` to implement `IntoIterator`
For E0277 on `for` loops, point at first line When E0277's span points at a `for` loop, the actual issue is in the element being iterated. Instead of pointing at the entire loop, point only at the first line (when possible) so that the span ends in the element for which E0277 was triggered. 2018-01-23 22:58:39 +00:00
Show number in error message even for one error Co-authored-by: Adrian <adrian.iosdev@gmail.com> 2023-11-21 15:44:16 +00:00			`error: aborting due to 1 previous error`
For E0277 on `for` loops, point at first line When E0277's span points at a `for` loop, the actual issue is in the element being iterated. Instead of pointing at the entire loop, point only at the first line (when possible) so that the span ends in the element for which E0277 was triggered. 2018-01-23 22:58:39 +00:00
update tests 2018-03-03 14:59:40 +00:00			For more information about this error, try `rustc --explain E0277`.