Mut restriction parse#156824
Open
CoCo-Japan-pan wants to merge 9 commits into
Open
Conversation
Collaborator
|
The parser was modified, potentially altering the grammar of (stable) Rust cc @fmease Changes to the size of AST and/or HIR nodes. cc @nnethercote The Rustfmt subtree was changed cc @rust-lang/rustfmt The Clippy subtree was changed cc @rust-lang/clippy |
Urgau
reviewed
May 22, 2026
fe707fe to
a594594
Compare
Urgau
approved these changes
May 23, 2026
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.
This PR is part of the progress implementing
mutrestrictions proposed in RFC 3323, and linked to a GSoC proposal.This PR focuses solely on the parsing of
mutrestrictions.The keyword order is
pub(...) mut(...) unsafe field.The new syntax is guared by
#[feature(mut_restriction)]feature gate.Tracking Issue: #105077
r? @Urgau
cc @jhpratt