[lex.phases] Use preprocessing token consistently #7361
Merged
Conversation
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
jensmaurer
reviewed
Oct 29, 2024
AlisdairM
force-pushed
the
clarify_pp_tokens
branch
from
712fc29 to
4ca51f4
Compare
Prior to converting preprocessing tokens to tokens in phase 7, all tokens are strictly preprocessing tokens. Add the missing qualification is appropriate through the phases of translation up to that point of conversion.
AlisdairM
force-pushed
the
clarify_pp_tokens
branch
from
4ca51f4 to
9234447
Compare
jensmaurer
approved these changes
Dec 19, 2024
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.
Prior to converting preprocessing tokens to tokens in phase 7, all tokens are strictly preprocessing tokens. Add the missing qualification is appropriate through the phases of translation up to that point of conversion.