Skip to content
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

Recover out of an enum or struct's braced block. #37245

Merged
merged 1 commit into from
Oct 27, 2016

Conversation

goffrie
Copy link
Contributor

@goffrie goffrie commented Oct 18, 2016

If we encounter a syntax error inside of a braced block, then we should
fail by consuming the rest of the block if possible.
This implements such recovery for enums and structs.

Fixes #37113.

@rust-highfive
Copy link
Collaborator

Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @nrc (or someone else) soon.

If any changes to this PR are deemed necessary, please add them as extra commits. This ensures that the reviewer can see what has changed since they last reviewed the code. Due to the way GitHub handles out-of-date commits, this should also make it reasonably obvious what issues have or haven't been addressed. Large or tricky changes may require several passes of review and changes.

Please see the contribution instructions for more information.

@nrc
Copy link
Member

nrc commented Oct 21, 2016

PR looks good. Could you add an extra test or two which have legal and illegal nesting of {}s please?

fields.push(self.parse_struct_decl_field()?);
fields.push(self.parse_struct_decl_field().map_err(|e| {
self.recover_stmt();
self.eat(&token::CloseDelim(token::Brace));
Copy link
Contributor

@jseyfried jseyfried Oct 21, 2016

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do we need to consume a } explicitly here?
If we leave the } unconsumed, it looks like we'd break out of the while loop and the } would get consumed by the self.bump(); call below.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Perhaps I should make this into a match to make it clearer. If there's an error then we'll hit an early return out of the function (? below).

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ahh yes, my bad. This is good as is, I was just confused.

If we encounter a syntax error inside of a braced block, then we should
fail by consuming the rest of the block if possible.
This implements such recovery for enums and structs.

Fixes rust-lang#37113.
@goffrie
Copy link
Contributor Author

goffrie commented Oct 27, 2016

I added another test, although I'm not totally sure what you mean by "legal and illegal nesting".

@nrc
Copy link
Member

nrc commented Oct 27, 2016

@bors: r+

@bors
Copy link
Contributor

bors commented Oct 27, 2016

📌 Commit c9036cc has been approved by nrc

@bors
Copy link
Contributor

bors commented Oct 27, 2016

⌛ Testing commit c9036cc with merge 0743694...

bors added a commit that referenced this pull request Oct 27, 2016
Recover out of an enum or struct's braced block.

If we encounter a syntax error inside of a braced block, then we should
fail by consuming the rest of the block if possible.
This implements such recovery for enums and structs.

Fixes #37113.
@bors bors merged commit c9036cc into rust-lang:master Oct 27, 2016
@goffrie goffrie deleted the recovery branch October 30, 2016 07:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants