rust-lang/rust
1
0
Fork 0
Code Issues Pull Requests Actions 1 Packages Projects Releases Wiki Activity
Files
901b340c1f5d208561d4261cc3ee634973b35326
rust/tests/ui/iterators/issue-28098.stderr

Ignoring revisions in .git-blame-ignore-revs. Click here to bypass and see the normal blame view.

78 lines
2.4 KiB
Plaintext
Raw Normal View History

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 18:53:53 -07:00
error[E0277]: `()` is not an iterator
When possible point at argument causing item obligation failure
2019-09-15 21:58:20 -07:00
--> $DIR/issue-28098.rs:2:28
Move some `compile-fail` tests to `ui`
2018-07-15 14:11:54 -07:00
|
LL | let _ = Iterator::next(&mut ());
Point at call span that introduced obligation for the arg
2021-09-07 11:30:53 +00:00
| -------------- ^^^^^^^ `()` is not an iterator
| |
| required by a bound introduced by this call
Move some `compile-fail` tests to `ui`
2018-07-15 14:11:54 -07: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 10:40:56 +03:00
= help: the trait `Iterator` is not implemented for `()`
Move some `compile-fail` tests to `ui`
2018-07-15 14:11:54 -07:00
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 18:53:53 -07:00
error[E0277]: `bool` is not an iterator
Deduplicate more sized errors on call exprs Change the implicit `Sized` `Obligation` `Span` for call expressions to include the whole expression. This aids the existing deduplication machinery to reduce the number of errors caused by a single unsized expression.
2024-01-24 02:52:29 +00:00
--> $DIR/issue-28098.rs:6:14
Move some `compile-fail` tests to `ui`
2018-07-15 14:11:54 -07:00
|
LL | for _ in false {}
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 18:53:53 -07:00
| ^^^^^ `bool` is not an iterator
Move some `compile-fail` tests to `ui`
2018-07-15 14:11:54 -07:00
|
Remove detail from label/note that is already available in other note Remove the "which is required by `{root_obligation}`" post-script in "the trait `X` is not implemented for `Y`" explanation in E0277. This information is already conveyed in the notes explaining requirements, making it redundant while making the text (particularly in labels) harder to read. ``` error[E0277]: the trait bound `NotCopy: Copy` is not satisfied --> $DIR/wf-static-type.rs:10:13 | LL | static FOO: IsCopy<Option<NotCopy>> = IsCopy { t: None }; | ^^^^^^^^^^^^^^^^^^^^^^^ the trait `Copy` is not implemented for `NotCopy` | = note: required for `Option<NotCopy>` to implement `Copy` note: required by a bound in `IsCopy` --> $DIR/wf-static-type.rs:7:17 | LL | struct IsCopy<T:Copy> { t: T } | ^^^^ required by this bound in `IsCopy` ``` vs the prior ``` error[E0277]: the trait bound `NotCopy: Copy` is not satisfied --> $DIR/wf-static-type.rs:10:13 | LL | static FOO: IsCopy<Option<NotCopy>> = IsCopy { t: None }; | ^^^^^^^^^^^^^^^^^^^^^^^ the trait `Copy` is not implemented for `NotCopy`, which is required by `Option<NotCopy>: Copy` | = note: required for `Option<NotCopy>` to implement `Copy` note: required by a bound in `IsCopy` --> $DIR/wf-static-type.rs:7:17 | LL | struct IsCopy<T:Copy> { t: T } | ^^^^ required by this bound in `IsCopy` ```
2024-10-24 21:14:17 +00:00
= help: the trait `Iterator` is not implemented for `bool`
Reword "Required because of the requirements on the impl of ..."
2022-08-15 21:31:37 +01:00
= note: required for `bool` to implement `IntoIterator`
Move some `compile-fail` tests to `ui`
2018-07-15 14:11:54 -07:00
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 18:53:53 -07:00
error[E0277]: `()` is not an iterator
Deduplicate more sized errors on call exprs Change the implicit `Sized` `Obligation` `Span` for call expressions to include the whole expression. This aids the existing deduplication machinery to reduce the number of errors caused by a single unsized expression.
2024-01-24 02:52:29 +00:00
--> $DIR/issue-28098.rs:9:28
Move some `compile-fail` tests to `ui`
2018-07-15 14:11:54 -07:00
|
LL | let _ = Iterator::next(&mut ());
Point at call span that introduced obligation for the arg
2021-09-07 11:30:53 +00:00
| -------------- ^^^^^^^ `()` is not an iterator
| |
| required by a bound introduced by this call
Move some `compile-fail` tests to `ui`
2018-07-15 14:11:54 -07: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 10:40:56 +03:00
= help: the trait `Iterator` is not implemented for `()`
Move some `compile-fail` tests to `ui`
2018-07-15 14:11:54 -07:00
Revert "Remove deferred sized checks" This reverts commit 33212bf7f527798a8cfa2bbb38781742f4ca718a.
2022-08-24 18:36:44 +00:00
error[E0277]: `()` is not an iterator
--> $DIR/issue-28098.rs:2:13
|
LL | let _ = Iterator::next(&mut ());
Deduplicate more sized errors on call exprs Change the implicit `Sized` `Obligation` `Span` for call expressions to include the whole expression. This aids the existing deduplication machinery to reduce the number of errors caused by a single unsized expression.
2024-01-24 02:52:29 +00:00
| ^^^^^^^^^^^^^^^^^^^^^^^ `()` is not an iterator
Revert "Remove deferred sized checks" This reverts commit 33212bf7f527798a8cfa2bbb38781742f4ca718a.
2022-08-24 18:36:44 +00:00
|
= help: the trait `Iterator` is not implemented for `()`
error[E0277]: `()` is not an iterator
Deduplicate more sized errors on call exprs Change the implicit `Sized` `Obligation` `Span` for call expressions to include the whole expression. This aids the existing deduplication machinery to reduce the number of errors caused by a single unsized expression.
2024-01-24 02:52:29 +00:00
--> $DIR/issue-28098.rs:18:28
When possible point at argument causing item obligation failure
2019-09-15 21:58:20 -07:00
|
LL | let _ = Iterator::next(&mut ());
Point at call span that introduced obligation for the arg
2021-09-07 11:30:53 +00:00
| -------------- ^^^^^^^ `()` is not an iterator
| |
| required by a bound introduced by this call
When possible point at argument causing item obligation failure
2019-09-15 21:58:20 -07: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 10:40:56 +03:00
= help: the trait `Iterator` is not implemented for `()`
Move some `compile-fail` tests to `ui`
2018-07-15 14:11:54 -07:00
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 18:53:53 -07:00
error[E0277]: `()` is not an iterator
Deduplicate more sized errors on call exprs Change the implicit `Sized` `Obligation` `Span` for call expressions to include the whole expression. This aids the existing deduplication machinery to reduce the number of errors caused by a single unsized expression.
2024-01-24 02:52:29 +00:00
--> $DIR/issue-28098.rs:22:28
Move some `compile-fail` tests to `ui`
2018-07-15 14:11:54 -07:00
|
LL | let _ = Iterator::next(&mut ());
Point at call span that introduced obligation for the arg
2021-09-07 11:30:53 +00:00
| -------------- ^^^^^^^ `()` is not an iterator
| |
| required by a bound introduced by this call
Move some `compile-fail` tests to `ui`
2018-07-15 14:11:54 -07: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 10:40:56 +03:00
= help: the trait `Iterator` is not implemented for `()`
Move some `compile-fail` tests to `ui`
2018-07-15 14:11:54 -07:00
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 18:53:53 -07:00
error[E0277]: `bool` is not an iterator
Deduplicate more sized errors on call exprs Change the implicit `Sized` `Obligation` `Span` for call expressions to include the whole expression. This aids the existing deduplication machinery to reduce the number of errors caused by a single unsized expression.
2024-01-24 02:52:29 +00:00
--> $DIR/issue-28098.rs:25:14
Move some `compile-fail` tests to `ui`
2018-07-15 14:11:54 -07:00
|
LL | for _ in false {}
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 18:53:53 -07:00
| ^^^^^ `bool` is not an iterator
Move some `compile-fail` tests to `ui`
2018-07-15 14:11:54 -07:00
|
Remove detail from label/note that is already available in other note Remove the "which is required by `{root_obligation}`" post-script in "the trait `X` is not implemented for `Y`" explanation in E0277. This information is already conveyed in the notes explaining requirements, making it redundant while making the text (particularly in labels) harder to read. ``` error[E0277]: the trait bound `NotCopy: Copy` is not satisfied --> $DIR/wf-static-type.rs:10:13 | LL | static FOO: IsCopy<Option<NotCopy>> = IsCopy { t: None }; | ^^^^^^^^^^^^^^^^^^^^^^^ the trait `Copy` is not implemented for `NotCopy` | = note: required for `Option<NotCopy>` to implement `Copy` note: required by a bound in `IsCopy` --> $DIR/wf-static-type.rs:7:17 | LL | struct IsCopy<T:Copy> { t: T } | ^^^^ required by this bound in `IsCopy` ``` vs the prior ``` error[E0277]: the trait bound `NotCopy: Copy` is not satisfied --> $DIR/wf-static-type.rs:10:13 | LL | static FOO: IsCopy<Option<NotCopy>> = IsCopy { t: None }; | ^^^^^^^^^^^^^^^^^^^^^^^ the trait `Copy` is not implemented for `NotCopy`, which is required by `Option<NotCopy>: Copy` | = note: required for `Option<NotCopy>` to implement `Copy` note: required by a bound in `IsCopy` --> $DIR/wf-static-type.rs:7:17 | LL | struct IsCopy<T:Copy> { t: T } | ^^^^ required by this bound in `IsCopy` ```
2024-10-24 21:14:17 +00:00
= help: the trait `Iterator` is not implemented for `bool`
Reword "Required because of the requirements on the impl of ..."
2022-08-15 21:31:37 +01:00
= note: required for `bool` to implement `IntoIterator`
Move some `compile-fail` tests to `ui`
2018-07-15 14:11:54 -07:00
Revert "Remove deferred sized checks" This reverts commit 33212bf7f527798a8cfa2bbb38781742f4ca718a.
2022-08-24 18:36:44 +00:00
error[E0277]: `()` is not an iterator
Deduplicate more sized errors on call exprs Change the implicit `Sized` `Obligation` `Span` for call expressions to include the whole expression. This aids the existing deduplication machinery to reduce the number of errors caused by a single unsized expression.
2024-01-24 02:52:29 +00:00
--> $DIR/issue-28098.rs:18:13
Revert "Remove deferred sized checks" This reverts commit 33212bf7f527798a8cfa2bbb38781742f4ca718a.
2022-08-24 18:36:44 +00:00
|
LL | let _ = Iterator::next(&mut ());
Deduplicate more sized errors on call exprs Change the implicit `Sized` `Obligation` `Span` for call expressions to include the whole expression. This aids the existing deduplication machinery to reduce the number of errors caused by a single unsized expression.
2024-01-24 02:52:29 +00:00
| ^^^^^^^^^^^^^^^^^^^^^^^ `()` is not an iterator
Revert "Remove deferred sized checks" This reverts commit 33212bf7f527798a8cfa2bbb38781742f4ca718a.
2022-08-24 18:36:44 +00:00
|
= help: the trait `Iterator` is not implemented for `()`
Deduplicate more sized errors on call exprs Change the implicit `Sized` `Obligation` `Span` for call expressions to include the whole expression. This aids the existing deduplication machinery to reduce the number of errors caused by a single unsized expression.
2024-01-24 02:52:29 +00:00
error: aborting due to 8 previous errors
Move some `compile-fail` tests to `ui`
2018-07-15 14:11:54 -07:00
For more information about this error, try `rustc --explain E0277`.
Reference in New Issue Copy Permalink