mikros/rust
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
887999d163
rust/src/test/ui/issues/issue-28344.stderr

35 lines
1.5 KiB
Plaintext
Raw Normal View History

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
error[E0191]: the value of the associated type `Output` (from trait `BitXor`) must be specified
Remove licenses
2018-12-25 09:56:47 -06:00
--> $DIR/issue-28344.rs:4:17
Move some `compile-fail` tests to `ui`
2018-07-15 16:11:54 -05:00
|
LL | let x: u8 = BitXor::bitor(0 as u8, 0 as u8);
Tweak errors for missing associated types and type parameters
2019-12-12 16:48:46 -06:00
| ^^^^^^ help: specify the associated type: `BitXor<Output = Type>`
Move some `compile-fail` tests to `ui`
2018-07-15 16:11:54 -05: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
error[E0599]: no function or associated item named `bitor` found for trait object `dyn BitXor<_>` in the current scope
Fixed more tests.
2018-12-07 12:15:36 -06:00
--> $DIR/issue-28344.rs:4:25
Move some `compile-fail` tests to `ui`
2018-07-15 16:11:54 -05:00
|
LL | let x: u8 = BitXor::bitor(0 as u8, 0 as u8);
Tweak spans for E0599
2019-03-10 18:20:15 -05: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
| function or associated item not found in `dyn BitXor<_>`
update tests
2020-03-04 21:03:15 -06:00
| help: there is an associated function with a similar name: `bitxor`
Move some `compile-fail` tests to `ui`
2018-07-15 16:11:54 -05: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
error[E0191]: the value of the associated type `Output` (from trait `BitXor`) must be specified
Remove licenses
2018-12-25 09:56:47 -06:00
--> $DIR/issue-28344.rs:8:13
Move some `compile-fail` tests to `ui`
2018-07-15 16:11:54 -05:00
|
LL | let g = BitXor::bitor;
Tweak errors for missing associated types and type parameters
2019-12-12 16:48:46 -06:00
| ^^^^^^ help: specify the associated type: `BitXor<Output = Type>`
Move some `compile-fail` tests to `ui`
2018-07-15 16:11:54 -05: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
error[E0599]: no function or associated item named `bitor` found for trait object `dyn BitXor<_>` in the current scope
Fixed more tests.
2018-12-07 12:15:36 -06:00
--> $DIR/issue-28344.rs:8:21
Move some `compile-fail` tests to `ui`
2018-07-15 16:11:54 -05:00
|
LL | let g = BitXor::bitor;
Tweak spans for E0599
2019-03-10 18:20:15 -05: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
| function or associated item not found in `dyn BitXor<_>`
update tests
2020-03-04 21:03:15 -06:00
| help: there is an associated function with a similar name: `bitxor`
Move some `compile-fail` tests to `ui`
2018-07-15 16:11:54 -05:00
error: aborting due to 4 previous errors
hide `--explain` hint if error has no extended info
2019-04-17 12:26:38 -05:00
Some errors have detailed explanations: E0191, E0599.
Move some `compile-fail` tests to `ui`
2018-07-15 16:11:54 -05:00
For more information about an error, try `rustc --explain E0191`.
Reference in New Issue Copy Permalink