Skip to content
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

change case classes and parser to support multi-ary \and/\or. #3676

Merged
merged 3 commits into from
Sep 28, 2023

Conversation

dwightguth
Copy link
Collaborator

At this stage, actually parsing a multi-ary term will lead to an internal representation that is handled incorrectly by all the code that interprets KORE. However, this change ought to pass CI and be sufficient to be able to modify the llvm backend without anything breaking.

At this stage, actually parsing a multi-ary term will lead to
an internal representation that is handled incorrectly by
all the code that interprets KORE. However, this change ought
to pass CI and be sufficient to be able to modify the llvm
backend without anything breaking.
@rv-jenkins rv-jenkins changed the base branch from master to develop September 28, 2023 17:48
Copy link
Collaborator

@Robertorosmaninho Robertorosmaninho left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM! Looking forward to the next steps!

@dwightguth dwightguth enabled auto-merge (squash) September 28, 2023 20:15
@dwightguth dwightguth merged commit 9ddff9d into develop Sep 28, 2023
@dwightguth dwightguth deleted the and_or branch September 28, 2023 20:36
dwightguth pushed a commit to runtimeverification/llvm-backend that referenced this pull request Sep 29, 2023
Blocked on runtimeverification/k#3676

This PR implements the changes to the scala code in the llvm backend to
support multi-ary and and or. In order to do this without the second
wave of changes to the frontend, we rely on a slightly messy approach
that involves breaking the abstraction barrier of the scala code in the
frontend. this will be cleaned up by a later PR that will revert the
first of the two commits in this PR.

---------

Co-authored-by: rv-jenkins <[email protected]>
@Baltoli Baltoli mentioned this pull request Dec 12, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants