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`
   = 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-09 20:53:53 -05:00			error[E0277]: `&str` is not an iterator
Fix tests from rebase 2020-09-07 04:01:45 -05: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 16:58:39 -06:00			`\|`
Update UI tests 2018-02-22 18:42:32 -06:00			`LL \| for c in "asdf" {`
Fix test after rebase 2018-02-01 16:16:53 -06: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 16:58:39 -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 `Iterator` is not implemented for `&str`
Reword "Required because of the requirements on the impl of ..." 2022-08-15 15:31:37 -05: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 16:58:39 -06: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`
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 16:58:39 -06:00
update tests 2018-03-03 08:59:40 -06:00			For more information about this error, try `rustc --explain E0277`.