-
Notifications
You must be signed in to change notification settings - Fork 12.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
E0507 E0009 should be mutually exclusive #64135
Labels
A-diagnostics
Area: Messages for errors, warnings, and lints
T-compiler
Relevant to the compiler team, which will review and decide on the PR/issue.
Comments
estebank
added
A-diagnostics
Area: Messages for errors, warnings, and lints
T-compiler
Relevant to the compiler team, which will review and decide on the PR/issue.
labels
Sep 3, 2019
CC #45600, which if it were fixed would also close this ticket. |
Centril
added a commit
to Centril/rust
that referenced
this issue
Sep 16, 2019
On obligation errors point at the unfulfilled binding when possible CC rust-lang#42855, rust-lang#64130, rust-lang#64135.
Centril
added a commit
to Centril/rust
that referenced
this issue
Sep 19, 2019
On obligation errors point at the unfulfilled binding when possible CC rust-lang#42855, rust-lang#64130, rust-lang#64135.
This is now resolved when you add |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
A-diagnostics
Area: Messages for errors, warnings, and lints
T-compiler
Relevant to the compiler team, which will review and decide on the PR/issue.
E0507 E0009 should be mutually exclusive
E0009
E0507
Example
Playground
Output
Reasoning
A situation where both trigger,
E0507
is a much more clear indication of something wrong in the code. In this example, the intention is thatAlmostCopy
implementsCopy
, and will subsequently trigger neither error. The presence ofE0009
is misleading when it doesn't include any mention ofCopy
without the click-through.The text was updated successfully, but these errors were encountered: