-
Notifications
You must be signed in to change notification settings - Fork 13.6k
librustc_lexer: Refactor the module #66015
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
Merged
Merged
Changes from 1 commit
Commits
Show all changes
9 commits
Select commit
Hold shift + click to select a range
0825b35
librustc_lexer: Add methods "first" and "second" to the "Cursor"
popzxc 72767a8
librustc_lexer: Introduce "eat_while" and "eat_identifier" methods
popzxc e0c45f7
librustc_lexer: Make "eat_float_exponent" return bool instead of result
popzxc 649a524
librustc_lexer: Simplify "single_quoted_string" method
popzxc d6f722d
librustc_lexer: Simplify "double_quoted_string" method
popzxc 6e350bd
librustc_lexer: Simplify "raw_double_quoted_string" method
popzxc ecd2673
librustc_lexer: Simplify "lifetime_or_char" method
popzxc e8b8d2a
librustc_lexer: Reorder imports in lib.rs
popzxc 31735b0
librustc_lexer: Make nth_char method private
popzxc File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
librustc_lexer: Simplify "lifetime_or_char" method
- Loading branch information
commit ecd26739d45837ee21fe0e2941f957086fbf6a47
There are no files selected for viewing
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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
By the way, I'm not sure why we're consuming the literal suffix above, but do not consume here.
As a result, we have a different errors for non-single character single-quoted literals with suffixes depending on the first symbol:
Playground 1 / Playground 2
That's pretty esoteric, I know, but nevertheless it seems a bit inconsistent to me.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
(I'm not sure if that can even be called a bug since the code in example is completely invalid)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think if we detect error in the char literal, it's better to recover the next token as identifier, rather than treat it as a suffix