mikros/rust
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
a733082be9
rust/tests/ui/derives/deriving-no-inner-impl-error-message.stderr

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

42 lines
1.5 KiB
Plaintext
Raw Normal View History

Moved compile-fail tests to ui tests.
2018-08-08 07:28:26 -05:00
error[E0369]: binary operation `==` cannot be applied to type `NoCloneOrEq`
Remove licenses
2018-12-25 09:56:47 -06:00
--> $DIR/deriving-no-inner-impl-error-message.rs:5:5
Moved compile-fail tests to ui tests.
2018-08-08 07:28:26 -05:00
|
Various diagnostics clean ups/tweaks * Always point at macros, including derive macros * Point at non-local items that introduce a trait requirement * On private associated item, point at definition
2021-07-17 13:13:50 -05:00
LL | #[derive(PartialEq)]
| --------- in this derive macro expansion
LL | struct E {
Update tests
2019-03-09 06:03:44 -06:00
LL | x: NoCloneOrEq
Moved compile-fail tests to ui tests.
2018-08-08 07:28:26 -05:00
| ^^^^^^^^^^^^^^
|
Provide RHS type hint when reporting operator error
2023-04-26 19:57:13 -05:00
note: an implementation of `PartialEq` might be missing for `NoCloneOrEq`
Consider unfulfilled obligations in binop errors When encountering a binop where the types would have been accepted, if all the predicates had been fulfilled, include information about the predicates and suggest appropriate `#[derive]`s if possible. Point at trait(s) that needs to be `impl`emented.
2021-09-28 09:48:54 -05:00
--> $DIR/deriving-no-inner-impl-error-message.rs:1:1
|
LL | struct NoCloneOrEq;
Provide RHS type hint when reporting operator error
2023-04-26 19:57:13 -05:00
| ^^^^^^^^^^^^^^^^^^ must implement `PartialEq`
Show macro name in 'this error originates in macro' message When there are multiple macros in use, it can be difficult to tell which one was responsible for producing an error.
2021-02-13 13:52:25 -06:00
= note: this error originates in the derive macro `PartialEq` (in Nightly builds, run with -Z macro-backtrace for more info)
Consider unfulfilled obligations in binop errors When encountering a binop where the types would have been accepted, if all the predicates had been fulfilled, include information about the predicates and suggest appropriate `#[derive]`s if possible. Point at trait(s) that needs to be `impl`emented.
2021-09-28 09:48:54 -05:00
help: consider annotating `NoCloneOrEq` with `#[derive(PartialEq)]`
|
Tweak output for 'add line' suggestion
2023-03-17 21:18:39 -05:00
LL + #[derive(PartialEq)]
LL | struct NoCloneOrEq;
Consider unfulfilled obligations in binop errors When encountering a binop where the types would have been accepted, if all the predicates had been fulfilled, include information about the predicates and suggest appropriate `#[derive]`s if possible. Point at trait(s) that needs to be `impl`emented.
2021-09-28 09:48:54 -05:00
|
Moved compile-fail tests to ui tests.
2018-08-08 07:28:26 -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[E0277]: the trait bound `NoCloneOrEq: Clone` is not satisfied
Don't derive `PartialEq::ne`. Currently we skip deriving `PartialEq::ne` for C-like (fieldless) enums and empty structs, thus reyling on the default `ne`. This behaviour is unnecessarily conservative, because the `PartialEq` docs say this: > Implementations must ensure that eq and ne are consistent with each other: > > `a != b` if and only if `!(a == b)` (ensured by the default > implementation). This means that the default implementation (`!(a == b)`) is always good enough. So this commit changes things such that `ne` is never derived. The motivation for this change is that not deriving `ne` reduces compile times and binary sizes. Observable behaviour may change if a user has defined a type `A` with an inconsistent `PartialEq` and then defines a type `B` that contains an `A` and also derives `PartialEq`. Such code is already buggy and preserving bug-for-bug compatibility isn't necessary. Two side-effects of the change: - There is only one error message produced for types where `PartialEq` cannot be derived, instead of two. - For coverage reports, some warnings about generated `ne` methods not being executed have disappeared. Both side-effects seem fine, and possibly preferable.
2022-06-22 01:11:14 -05:00
--> $DIR/deriving-no-inner-impl-error-message.rs:9:5
Moved compile-fail tests to ui tests.
2018-08-08 07:28:26 -05:00
|
Various diagnostics clean ups/tweaks * Always point at macros, including derive macros * Point at non-local items that introduce a trait requirement * On private associated item, point at definition
2021-07-17 13:13:50 -05:00
LL | #[derive(Clone)]
| ----- in this derive macro expansion
LL | struct C {
Moved compile-fail tests to ui tests.
2018-08-08 07:28:26 -05:00
LL | x: NoCloneOrEq
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
| ^^^^^^^^^^^^^^ the trait `Clone` is not implemented for `NoCloneOrEq`
Moved compile-fail tests to ui tests.
2018-08-08 07:28:26 -05:00
|
Show macro name in 'this error originates in macro' message When there are multiple macros in use, it can be difficult to tell which one was responsible for producing an error.
2021-02-13 13:52:25 -06:00
= note: this error originates in the derive macro `Clone` (in Nightly builds, run with -Z macro-backtrace for more info)
Suggest derivable trait on E0277
2022-03-31 09:58:45 -05:00
help: consider annotating `NoCloneOrEq` with `#[derive(Clone)]`
|
Tweak output for 'add line' suggestion
2023-03-17 21:18:39 -05:00
LL + #[derive(Clone)]
LL | struct NoCloneOrEq;
Suggest derivable trait on E0277
2022-03-31 09:58:45 -05:00
|
Moved compile-fail tests to ui tests.
2018-08-08 07:28:26 -05:00
Don't derive `PartialEq::ne`. Currently we skip deriving `PartialEq::ne` for C-like (fieldless) enums and empty structs, thus reyling on the default `ne`. This behaviour is unnecessarily conservative, because the `PartialEq` docs say this: > Implementations must ensure that eq and ne are consistent with each other: > > `a != b` if and only if `!(a == b)` (ensured by the default > implementation). This means that the default implementation (`!(a == b)`) is always good enough. So this commit changes things such that `ne` is never derived. The motivation for this change is that not deriving `ne` reduces compile times and binary sizes. Observable behaviour may change if a user has defined a type `A` with an inconsistent `PartialEq` and then defines a type `B` that contains an `A` and also derives `PartialEq`. Such code is already buggy and preserving bug-for-bug compatibility isn't necessary. Two side-effects of the change: - There is only one error message produced for types where `PartialEq` cannot be derived, instead of two. - For coverage reports, some warnings about generated `ne` methods not being executed have disappeared. Both side-effects seem fine, and possibly preferable.
2022-06-22 01:11:14 -05:00
error: aborting due to 2 previous errors
Moved compile-fail tests to ui tests.
2018-08-08 07:28:26 -05:00
hide `--explain` hint if error has no extended info
2019-04-17 12:26:38 -05:00
Some errors have detailed explanations: E0277, E0369.
Moved compile-fail tests to ui tests.
2018-08-08 07:28:26 -05:00
For more information about an error, try `rustc --explain E0277`.
Reference in New Issue Copy Permalink