Continue parsing function after finding ... arg#48154
Merged
kennytm merged 1 commit intorust-lang:masterfrom Feb 15, 2018
Merged
Continue parsing function after finding ... arg#48154kennytm merged 1 commit intorust-lang:masterfrom
... arg#48154kennytm merged 1 commit intorust-lang:masterfrom
Conversation
When encountering a variadic argument in a function definition that doesn't accept it, if immediately after there's a closing paren, continue parsing as normal. Otherwise keep current behavior of emitting error and stopping.
Contributor
|
r? @eddyb (rust_highfive has picked a reviewer for you, use r? to override) |
Member
Member
|
Would this conflict with RFC 2137 (#44930)? |
Contributor
Author
|
@kennytm it would have to be removed once that RFC is implemented. In the meantime the current error message is subpar as it swallows later, more relevant errors in the tested case. |
nikomatsakis
approved these changes
Feb 12, 2018
Contributor
|
@bors r+ |
Collaborator
|
📌 Commit f7cabc6 has been approved by |
Contributor
Author
|
@bors rollup |
kennytm
added a commit
to kennytm/rust
that referenced
this pull request
Feb 13, 2018
Continue parsing function after finding `...` arg When encountering a variadic argument in a function definition that doesn't accept it, if immediately after there's a closing paren, continue parsing as normal. Otherwise keep current behavior of emitting error and stopping. Fix rust-lang#31481.
kennytm
added a commit
to kennytm/rust
that referenced
this pull request
Feb 14, 2018
Continue parsing function after finding `...` arg When encountering a variadic argument in a function definition that doesn't accept it, if immediately after there's a closing paren, continue parsing as normal. Otherwise keep current behavior of emitting error and stopping. Fix rust-lang#31481.
bors
added a commit
that referenced
this pull request
Feb 14, 2018
bors
added a commit
that referenced
this pull request
Feb 15, 2018
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
When encountering a variadic argument in a function definition that
doesn't accept it, if immediately after there's a closing paren,
continue parsing as normal. Otherwise keep current behavior of emitting
error and stopping.
Fix #31481.