feat: add parse package
#406
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
Merged
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.
Fixes #405
This adds the new
@sdeverywhere/parsepackage to the repo, but does not include any changes to existing code (that will come in subsequent issues and PRs). See issue for more details.@ToddFincannonEI: I'm adding you as reviewer, but it's up to you how much or little you'd like to review this new code. Let me know if you'd like an overview or tour. It'll also hopefully be more clear how it fits together when I submit the next PR, which updates the
compilepackage to make use of this newparsepackage.One thing to note is that I'm not intending for this new package to be a public-facing package right away, so the API docs are not published and it's treated more like an implementation detail of the
compilepackage for now. Some of the AST node types aren't perfect yet and I have some names I'd like to change to better align with XMILE terminology, but I figure that can happen later.