mikros/rust
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
10b08e3c9c
rust/tests/ui/derives/derives-span-PartialEq-tuple-struct.stderr

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

24 lines
796 B
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 `Error`
tests: remove ignore directives from tests that mention core/alloc/std spans.
2020-03-31 20:10:13 -05:00
--> $DIR/derives-span-PartialEq-tuple-struct.rs:8: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 Struct(
Update tests
2019-03-09 06:03:44 -06:00
LL | Error
Moved compile-fail tests to ui tests.
2018-08-08 07:28:26 -05:00
| ^^^^^
|
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
note: an implementation of `PartialEq<_>` might be missing for `Error`
--> $DIR/derives-span-PartialEq-tuple-struct.rs:4:1
|
LL | struct Error;
Shorten def_span for more items.
2022-02-13 09:27:59 -06: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 `Error` with `#[derive(PartialEq)]`
|
LL | #[derive(PartialEq)]
|
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 previous error
Moved compile-fail tests to ui tests.
2018-08-08 07:28:26 -05:00
For more information about this error, try `rustc --explain E0369`.
Reference in New Issue Copy Permalink