Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.
Sign upFriendlier compiler message for incorrect trait method signatures #28011
Comments
jdm
added
the
A-diagnostics
label
Aug 26, 2015
This comment has been minimized.
This comment has been minimized.
|
I wanted similar behaviour occasionally as well. Looking signatures up in the docs is painful. |
This comment has been minimized.
This comment has been minimized.
|
related: #24626, which requests the same for missing methods in impls. |
estebank
added a commit
to estebank/rust
that referenced
this issue
Sep 10, 2016
estebank
added a commit
to estebank/rust
that referenced
this issue
Sep 10, 2016
estebank
referenced this issue
Sep 10, 2016
Closed
Include type of missing trait methods in error #36371
estebank
added a commit
to estebank/rust
that referenced
this issue
Oct 1, 2016
This comment has been minimized.
This comment has been minimized.
|
Related: #37370. |
steveklabnik
removed
the
T-compiler
label
Mar 9, 2017
This comment has been minimized.
This comment has been minimized.
|
Worth pointing out that the signature is relatively easy to get today if the method is removed. Still a problem though. |
estebank
referenced this issue
Jun 1, 2017
Merged
Show trait method signature when impl differs #42362
bors
added a commit
that referenced
this issue
Jun 4, 2017
bors
closed this
in
#42362
Jun 4, 2017
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
andersforsgren commentedAug 26, 2015
When implementing a trait, it would be useful to see the expected method signature in compiler error messages. Example
The current error message for E0186 only lets me partially resolve the issue:
It would be more friendly to the user if the message showed both the actual and expected method signatures.