mikros/rust
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
a20078f044
rust/tests/ui/impl-trait/issues/infinite-impl-trait-issue-38064.stderr

28 lines
843 B
Plaintext
Raw Normal View History

review comments
2020-06-15 14:11:28 -05:00
error[E0720]: cannot resolve opaque type
Forbid impl Trait from referring to unnamable recursive types There is no type T, such that `T = [T; 2]`, we should not allow this to be circumvented by impl Trait.
2018-11-18 12:33:44 -06:00
--> $DIR/infinite-impl-trait-issue-38064.rs:8:13
Moved compile-fail tests to ui tests.
2018-08-08 07:28:26 -05:00
|
Update tests
2019-03-09 06:03:44 -06:00
LL | fn foo() -> impl Quux {
Expand "recursive opaque type" diagnostic Fix #70968, partially address #66523.
2020-04-19 18:52:15 -05:00
| ^^^^^^^^^ recursive opaque type
...
LL | Foo(bar())
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
| ---------- returning here with type `Foo<impl Quux>`
Expand "recursive opaque type" diagnostic Fix #70968, partially address #66523.
2020-04-19 18:52:15 -05:00
...
LL | fn bar() -> impl Quux {
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
| --------- returning this opaque type `Foo<impl Quux>`
Forbid impl Trait from referring to unnamable recursive types There is no type T, such that `T = [T; 2]`, we should not allow this to be circumvented by impl Trait.
2018-11-18 12:33:44 -06:00
review comments
2020-06-15 14:11:28 -05:00
error[E0720]: cannot resolve opaque type
Forbid impl Trait from referring to unnamable recursive types There is no type T, such that `T = [T; 2]`, we should not allow this to be circumvented by impl Trait.
2018-11-18 12:33:44 -06:00
--> $DIR/infinite-impl-trait-issue-38064.rs:14:13
|
Expand "recursive opaque type" diagnostic Fix #70968, partially address #66523.
2020-04-19 18:52:15 -05:00
LL | fn foo() -> impl Quux {
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
| --------- returning this opaque type `Bar<impl Quux>`
Expand "recursive opaque type" diagnostic Fix #70968, partially address #66523.
2020-04-19 18:52:15 -05:00
...
Update tests
2019-03-09 06:03:44 -06:00
LL | fn bar() -> impl Quux {
Expand "recursive opaque type" diagnostic Fix #70968, partially address #66523.
2020-04-19 18:52:15 -05:00
| ^^^^^^^^^ recursive opaque type
...
LL | Bar(foo())
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
| ---------- returning here with type `Bar<impl Quux>`
Moved compile-fail tests to ui tests.
2018-08-08 07:28:26 -05:00
Forbid impl Trait from referring to unnamable recursive types There is no type T, such that `T = [T; 2]`, we should not allow this to be circumvented by impl Trait.
2018-11-18 12:33:44 -06:00
error: aborting due to 2 previous errors
Moved compile-fail tests to ui tests.
2018-08-08 07:28:26 -05:00
Forbid impl Trait from referring to unnamable recursive types There is no type T, such that `T = [T; 2]`, we should not allow this to be circumvented by impl Trait.
2018-11-18 12:33:44 -06:00
For more information about this error, try `rustc --explain E0720`.
Reference in New Issue Copy Permalink