update scala kore parser to use multi-ary and and or everywhere#3678
Merged
dwightguth merged 6 commits intodevelopfrom Oct 2, 2023
Merged
update scala kore parser to use multi-ary and and or everywhere#3678dwightguth merged 6 commits intodevelopfrom
dwightguth merged 6 commits intodevelopfrom
Conversation
Robertorosmaninho
approved these changes
Sep 29, 2023
Collaborator
|
Is it possible to have some documentation on these pattern matchings? They're starting to be confusing, at least for me, as I don't touch this part of the code often. |
5 tasks
Closed
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Blocked on runtimeverification/llvm-backend#842
This is the second wave of changes to the frontend to update the scala parser to uses multi-ary and and or. This now completes the changes to the frontend except that we will need one minor third PR to make the class we made public private again after making the second wave of changes to the llvm backend.