nordic-dev.net/rust
nordic-dev.net/rust
2
0
Fork 0
mirror of https://github.com/rust-lang/rust.git synced 2024-11-23 07:14:28 +00:00
Code Issues Packages Projects Releases Wiki Activity
6fc50dacd4
rust/tests/ui/iterators/issue-28098.stderr

110 lines
3.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-10 01:53:53 +00:00
error[E0277]: `()` is not an iterator
When possible point at argument causing item obligation failure
2019-09-16 04:58:20 +00:00
--> $DIR/issue-28098.rs:2:28
Move some `compile-fail` tests to `ui`
2018-07-15 21:11:54 +00: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 21:11:54 +00: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 07:40:56 +00:00
= help: the trait `Iterator` is not implemented for `()`
Move some `compile-fail` tests to `ui`
2018-07-15 21:11:54 +00: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 ());
| ^^^^^^^^^^^^^^^^^^^^^^^ `()` is not an iterator
|
= help: the trait `Iterator` is not implemented for `()`
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]: `bool` is not an iterator
Revert "Remove deferred sized checks" This reverts commit 33212bf7f527798a8cfa2bbb38781742f4ca718a.
2022-08-24 18:36:44 +00:00
--> $DIR/issue-28098.rs:7:14
Move some `compile-fail` tests to `ui`
2018-07-15 21:11:54 +00: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-10 01:53:53 +00:00
| ^^^^^ `bool` is not an iterator
Move some `compile-fail` tests to `ui`
2018-07-15 21:11:54 +00:00
|
Fix tests from rebase
2020-09-07 09:01:45 +00:00
= help: the trait `Iterator` is not implemented for `bool`
Reword "Required because of the requirements on the impl of ..."
2022-08-15 20:31:37 +00:00
= note: required for `bool` to implement `IntoIterator`
Move some `compile-fail` tests to `ui`
2018-07-15 21:11:54 +00: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-10 01:53:53 +00:00
error[E0277]: `()` is not an iterator
Revert "Remove deferred sized checks" This reverts commit 33212bf7f527798a8cfa2bbb38781742f4ca718a.
2022-08-24 18:36:44 +00:00
--> $DIR/issue-28098.rs:10:28
Move some `compile-fail` tests to `ui`
2018-07-15 21:11:54 +00: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 21:11:54 +00: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 07:40:56 +00:00
= help: the trait `Iterator` is not implemented for `()`
Move some `compile-fail` tests to `ui`
2018-07-15 21:11:54 +00: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-10 01:53:53 +00:00
error[E0277]: `()` is not an iterator
Revert "Remove deferred sized checks" This reverts commit 33212bf7f527798a8cfa2bbb38781742f4ca718a.
2022-08-24 18:36:44 +00:00
--> $DIR/issue-28098.rs:10:13
|
LL | let _ = Iterator::next(&mut ());
| ^^^^^^^^^^^^^^^^^^^^^^^ `()` is not an iterator
|
= help: the trait `Iterator` is not implemented for `()`
error[E0277]: `()` is not an iterator
--> $DIR/issue-28098.rs:2:13
|
LL | let _ = Iterator::next(&mut ());
| ^^^^^^^^^^^^^^ `()` is not an iterator
|
= help: the trait `Iterator` is not implemented for `()`
error[E0277]: `()` is not an iterator
--> $DIR/issue-28098.rs:20:28
When possible point at argument causing item obligation failure
2019-09-16 04:58:20 +00: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-16 04:58:20 +00: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 07:40:56 +00:00
= help: the trait `Iterator` is not implemented for `()`
Move some `compile-fail` tests to `ui`
2018-07-15 21:11:54 +00: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-10 01:53:53 +00:00
error[E0277]: `()` is not an iterator
Revert "Remove deferred sized checks" This reverts commit 33212bf7f527798a8cfa2bbb38781742f4ca718a.
2022-08-24 18:36:44 +00:00
--> $DIR/issue-28098.rs:20:13
|
LL | let _ = Iterator::next(&mut ());
| ^^^^^^^^^^^^^^^^^^^^^^^ `()` is not an iterator
|
= help: the trait `Iterator` is not implemented for `()`
error[E0277]: `()` is not an iterator
--> $DIR/issue-28098.rs:25:28
Move some `compile-fail` tests to `ui`
2018-07-15 21:11:54 +00: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 21:11:54 +00: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 07:40:56 +00:00
= help: the trait `Iterator` is not implemented for `()`
Move some `compile-fail` tests to `ui`
2018-07-15 21:11:54 +00: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:25:13
|
LL | let _ = Iterator::next(&mut ());
| ^^^^^^^^^^^^^^^^^^^^^^^ `()` is not an iterator
|
= help: the trait `Iterator` is not implemented for `()`
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]: `bool` is not an iterator
Revert "Remove deferred sized checks" This reverts commit 33212bf7f527798a8cfa2bbb38781742f4ca718a.
2022-08-24 18:36:44 +00:00
--> $DIR/issue-28098.rs:29:14
Move some `compile-fail` tests to `ui`
2018-07-15 21:11:54 +00: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-10 01:53:53 +00:00
| ^^^^^ `bool` is not an iterator
Move some `compile-fail` tests to `ui`
2018-07-15 21:11:54 +00: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 07:40:56 +00:00
= help: the trait `Iterator` is not implemented for `bool`
Reword "Required because of the requirements on the impl of ..."
2022-08-15 20:31:37 +00:00
= note: required for `bool` to implement `IntoIterator`
Move some `compile-fail` tests to `ui`
2018-07-15 21:11:54 +00: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:20:13
|
LL | let _ = Iterator::next(&mut ());
| ^^^^^^^^^^^^^^ `()` is not an iterator
|
= help: the trait `Iterator` is not implemented for `()`
error: aborting due to 12 previous errors
Move some `compile-fail` tests to `ui`
2018-07-15 21:11:54 +00:00
For more information about this error, try `rustc --explain E0277`.
Reference in New Issue Copy Permalink