Bugfix: Allow rust tuple indexing #1580
Merged
Conversation
This file contains 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
hugopeixoto
changed the title
`lorem.0` is now supported
hugopeixoto
force-pushed
the
fix.rust-tuple-indexing
branch
from
ab91e84
to
f7a89c0
Compare
pyrmont
suggested changes
Sep 8, 2020
pyrmont
added
author-action
pyrmont
approved these changes
Sep 8, 2020
|
Thanks for adding this, too! |
pyrmont
removed
the
author-action
mattt
pushed a commit
to NSHipster/rouge
that referenced
this pull request
May 19, 2021
Currently, the Rust lexer does not support tuple index expressions. This commit adds that support. To differentiate between tuple index expressions and field access expressions, the `Name::Attribute` token is used. Co-authored-by: Michael Camilleri <mike@inqk.net>
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.
lorem.0is now supported.Fixes #958.