-
Notifications
You must be signed in to change notification settings - Fork 152
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
Encoding symbolic and concrete in Kore #3406
Comments
These should be enforced by the frontend. |
Will have to update KEVM to do this. |
Baltoli
pushed a commit
that referenced
this issue
Nov 1, 2023
…3085) * haskell-backend/src/main/native/haskell-backend: b88c128f3 - Transfer not simplified claims to applyClaim (#3398) * Sync flake inputs to submodules * haskell-backend/src/main/native/haskell-backend: 8352c471b - Remove `UnifierT` from `NotSimplifier` (#3404) * Sync flake inputs to submodules * haskell-backend/src/main/native/haskell-backend: 324773459 - Remove keys faster (#3395) * Sync flake inputs to submodules * haskell-backend/src/main/native/haskell-backend: 275afe775 - Monomorphization of Simplifier, leg 4 (#3408) * Sync flake inputs to submodules * haskell-backend/src/main/native/haskell-backend: 5a3472be3 - Update dependency: deps/k_release (#3406) * Sync flake inputs to submodules Co-authored-by: rv-jenkins <devops@runtimeverification.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
K currently allows users to mark function definition rules as symbolic or concrete. Since function definitions have semantic value, the symbolic and concrete attribute need to have an encoding in Kore/ML. We need to figure out if our main semantics use this feature, and if they do, to figure out if such an encoding exists.
Note: this is for function definition rules not simplification rules
Related #3385
The text was updated successfully, but these errors were encountered: