PEGTL Path Parser Extraction #2822
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
erslavin
force-pushed
the
path_parser
branch
from
361b366
to
82f305c
Compare
|
Filed as internal issue #USD-8973 |
nvmkuruc
force-pushed
the
path_parser
branch
from
82f305c
to
9ed0ea6
Compare
crevilla
reviewed
Nov 28, 2023
crevilla
reviewed
Nov 28, 2023
crevilla
reviewed
Nov 28, 2023
- Separated out existing PEGTL path parser into its own set of header / source files in preparation for it to be used directly in a PEGTL based text file format parser - Explicitly namespaced PEGTL types
erslavin
force-pushed
the
path_parser
branch
from
9ed0ea6
to
56ad471
Compare
sunyab
added
the
usd-utf8-identifiers
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.
Description of Change(s)
Fixes Issue(s)