-
Notifications
You must be signed in to change notification settings - Fork 13k
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
2018 edition - confusing error message when declaring unnamed parameters #56584
Conversation
r? @eddyb (rust_highfive has picked a reviewer for you, use r? to override) |
This comment has been minimized.
This comment has been minimized.
This commit adds a note providing context for the change to argument names being required in the 2018 edition for trait methods.
This commit emits a suggestion for adding an underscore binding to arguments in trait methods that previously did not have a argument name specified.
9d1f89e
to
7fcf31b
Compare
Ah, good point @Nemo157. I've updated the messages. |
@bors r+ |
📌 Commit 7fcf31b has been approved by |
⌛ Testing commit 7fcf31b with merge e8c8d274b0b611a5d4711af6095d477729436e30... |
💔 Test failed - status-appveyor |
Your PR failed on Travis (raw log). Through arcane magic we have determined that the following fragments from the build log may contain information about the problem. Click to expand the log.
I'm a bot! I can only do what humans tell me to, so if this was not helpful or you have suggestions for improvements, please ping or otherwise contact |
@bors: retry
|
2018 edition - confusing error message when declaring unnamed parameters Fixes #53990. This PR adds a note providing context for the change to argument names being required in the 2018 edition for trait methods and a suggestion for the fix.
☀️ Test successful - status-appveyor, status-travis |
Fixes #53990.
This PR adds a note providing context for the change to argument
names being required in the 2018 edition for trait methods and a
suggestion for the fix.