mathieu/os-rust
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
os-rust/tests/ui/issues/issue-28344.stderr

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

62 lines
2.6 KiB
Text
Raw Normal View History

Lint bare traits in AstConv.
2021-07-10 10:00:54 +02:00
warning: trait objects without an explicit `dyn` are deprecated
--> $DIR/issue-28344.rs:4:17
|
LL | let x: u8 = BitXor::bitor(0 as u8, 0 as u8);
Use multipart suggestions.
2021-11-01 10:01:42 +01:00
| ^^^^^^
Lint bare traits in AstConv.
2021-07-10 10:00:54 +02:00
|
= warning: this is accepted in the current edition (Rust 2015) but is a hard error in Rust 2021!
= note: for more information, see <https://doc.rust-lang.org/nightly/edition-guide/rust-2021/warnings-promoted-to-error.html>
bless ui tests
2022-09-18 19:55:36 +04:00
= note: `#[warn(bare_trait_objects)]` on by default
Compiler: Rename "object safe" to "dyn compatible"
2024-09-25 10:38:40 +02:00
help: if this is a dyn-compatible trait, use `dyn`
Use multipart suggestions.
2021-11-01 10:01:42 +01:00
|
LL | let x: u8 = <dyn BitXor>::bitor(0 as u8, 0 as u8);
| ++++ +
Lint bare traits in AstConv.
2021-07-10 10:00:54 +02:00
Detect object safety errors when assoc type is missing When an associated type with GATs isn't specified in a `dyn Trait`, emit an object safety error instead of only complaining about the missing associated type, as it will lead the user down a path of three different errors before letting them know that what they were trying to do is impossible to begin with. Fix #103155.
2023-10-04 01:10:51 +00:00
error[E0191]: the value of the associated type `Output` in `BitXor` must be specified
Remove licenses
2018-12-25 08:56:47 -07:00
--> $DIR/issue-28344.rs:4:17
Move some `compile-fail` tests to `ui`
2018-07-15 14:11:54 -07:00
|
LL | let x: u8 = BitXor::bitor(0 as u8, 0 as u8);
E0191 suggestion correction, inserts turbofish without dyn (#91997)
2024-07-09 17:21:31 -06:00
| ^^^^^^ help: specify the associated type: `BitXor::<Output = Type>`
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
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 18:15:36 +00:00
--> $DIR/issue-28344.rs:4:25
Move some `compile-fail` tests to `ui`
2018-07-15 14:11:54 -07:00
|
LL | let x: u8 = BitXor::bitor(0 as u8, 0 as u8);
Consider methods from traits when suggesting typos Do not provide a structured suggestion when the arguments don't match. ``` error[E0599]: no method named `test_mut` found for struct `Vec<{integer}>` in the current scope --> $DIR/auto-ref-slice-plus-ref.rs:7:7 | LL | a.test_mut(); | ^^^^^^^^ | = help: items from traits can only be used if the trait is implemented and in scope note: `MyIter` defines an item `test_mut`, perhaps you need to implement it --> $DIR/auto-ref-slice-plus-ref.rs:14:1 | LL | trait MyIter { | ^^^^^^^^^^^^ help: there is a method `get_mut` with a similar name, but with different arguments --> $SRC_DIR/core/src/slice/mod.rs:LL:COL ``` Consider methods beyond inherent ones when suggesting typos. ``` error[E0599]: no method named `owned` found for reference `&dyn Foo` in the current scope --> $DIR/object-pointer-types.rs:11:7 | LL | fn owned(self: Box<Self>); | --------- the method might not be found because of this arbitrary self type ... LL | x.owned(); | ^^^^^ help: there is a method with a similar name: `to_owned` ``` Fix #101013.
2024-02-10 03:33:20 +00:00
| ^^^^^ function or associated item not found in `dyn BitXor<_>`
|
help: there is a method `bitxor` with a similar name, but with different arguments
--> $SRC_DIR/core/src/ops/bit.rs:LL:COL
Move some `compile-fail` tests to `ui`
2018-07-15 14:11:54 -07:00
Lint bare traits in AstConv.
2021-07-10 10:00:54 +02:00
warning: trait objects without an explicit `dyn` are deprecated
--> $DIR/issue-28344.rs:10:13
|
LL | let g = BitXor::bitor;
Use multipart suggestions.
2021-11-01 10:01:42 +01:00
| ^^^^^^
Lint bare traits in AstConv.
2021-07-10 10:00:54 +02:00
|
= warning: this is accepted in the current edition (Rust 2015) but is a hard error in Rust 2021!
= note: for more information, see <https://doc.rust-lang.org/nightly/edition-guide/rust-2021/warnings-promoted-to-error.html>
Compiler: Rename "object safe" to "dyn compatible"
2024-09-25 10:38:40 +02:00
help: if this is a dyn-compatible trait, use `dyn`
Use multipart suggestions.
2021-11-01 10:01:42 +01:00
|
LL | let g = <dyn BitXor>::bitor;
| ++++ +
Lint bare traits in AstConv.
2021-07-10 10:00:54 +02:00
Detect object safety errors when assoc type is missing When an associated type with GATs isn't specified in a `dyn Trait`, emit an object safety error instead of only complaining about the missing associated type, as it will lead the user down a path of three different errors before letting them know that what they were trying to do is impossible to begin with. Fix #103155.
2023-10-04 01:10:51 +00:00
error[E0191]: the value of the associated type `Output` in `BitXor` must be specified
Lint bare traits in AstConv.
2021-07-10 10:00:54 +02:00
--> $DIR/issue-28344.rs:10:13
Move some `compile-fail` tests to `ui`
2018-07-15 14:11:54 -07:00
|
LL | let g = BitXor::bitor;
E0191 suggestion correction, inserts turbofish without dyn (#91997)
2024-07-09 17:21:31 -06:00
| ^^^^^^ help: specify the associated type: `BitXor::<Output = Type>`
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
error[E0599]: no function or associated item named `bitor` found for trait object `dyn BitXor<_>` in the current scope
Lint bare traits in AstConv.
2021-07-10 10:00:54 +02:00
--> $DIR/issue-28344.rs:10:21
Move some `compile-fail` tests to `ui`
2018-07-15 14:11:54 -07:00
|
LL | let g = BitXor::bitor;
Consider methods from traits when suggesting typos Do not provide a structured suggestion when the arguments don't match. ``` error[E0599]: no method named `test_mut` found for struct `Vec<{integer}>` in the current scope --> $DIR/auto-ref-slice-plus-ref.rs:7:7 | LL | a.test_mut(); | ^^^^^^^^ | = help: items from traits can only be used if the trait is implemented and in scope note: `MyIter` defines an item `test_mut`, perhaps you need to implement it --> $DIR/auto-ref-slice-plus-ref.rs:14:1 | LL | trait MyIter { | ^^^^^^^^^^^^ help: there is a method `get_mut` with a similar name, but with different arguments --> $SRC_DIR/core/src/slice/mod.rs:LL:COL ``` Consider methods beyond inherent ones when suggesting typos. ``` error[E0599]: no method named `owned` found for reference `&dyn Foo` in the current scope --> $DIR/object-pointer-types.rs:11:7 | LL | fn owned(self: Box<Self>); | --------- the method might not be found because of this arbitrary self type ... LL | x.owned(); | ^^^^^ help: there is a method with a similar name: `to_owned` ``` Fix #101013.
2024-02-10 03:33:20 +00:00
| ^^^^^ function or associated item not found in `dyn BitXor<_>`
|
Remove a bunch of redundant args from report_method_error
2024-06-02 21:19:11 -04:00
help: there is a method `bitxor` with a similar name
Consider methods from traits when suggesting typos Do not provide a structured suggestion when the arguments don't match. ``` error[E0599]: no method named `test_mut` found for struct `Vec<{integer}>` in the current scope --> $DIR/auto-ref-slice-plus-ref.rs:7:7 | LL | a.test_mut(); | ^^^^^^^^ | = help: items from traits can only be used if the trait is implemented and in scope note: `MyIter` defines an item `test_mut`, perhaps you need to implement it --> $DIR/auto-ref-slice-plus-ref.rs:14:1 | LL | trait MyIter { | ^^^^^^^^^^^^ help: there is a method `get_mut` with a similar name, but with different arguments --> $SRC_DIR/core/src/slice/mod.rs:LL:COL ``` Consider methods beyond inherent ones when suggesting typos. ``` error[E0599]: no method named `owned` found for reference `&dyn Foo` in the current scope --> $DIR/object-pointer-types.rs:11:7 | LL | fn owned(self: Box<Self>); | --------- the method might not be found because of this arbitrary self type ... LL | x.owned(); | ^^^^^ help: there is a method with a similar name: `to_owned` ``` Fix #101013.
2024-02-10 03:33:20 +00:00
--> $SRC_DIR/core/src/ops/bit.rs:LL:COL
Move some `compile-fail` tests to `ui`
2018-07-15 14:11:54 -07:00
Lint bare traits in AstConv.
2021-07-10 10:00:54 +02:00
error: aborting due to 4 previous errors; 2 warnings emitted
Move some `compile-fail` tests to `ui`
2018-07-15 14:11:54 -07:00
hide `--explain` hint if error has no extended info
2019-04-17 13:26:38 -04:00
Some errors have detailed explanations: E0191, E0599.
Move some `compile-fail` tests to `ui`
2018-07-15 14:11:54 -07:00
For more information about an error, try `rustc --explain E0191`.
Reference in a new issue Copy permalink