Skip to content

Add support for rawTerm to Python bindings #908

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

Merged
merged 5 commits into from
Dec 5, 2023
Merged

Conversation

Baltoli
Copy link
Contributor

@Baltoli Baltoli commented Nov 28, 2023

Blocked on #907

This PR follows up #907 by having the Python bindings strip patterns of the form rawTerm{}(inj{...}(...)}) when deserializing from binary KORE; this will allow Pyk and subsequently the proof checker's parser to soundly load function arguments from proof traces and pass them to the function evaluator in #905.

@Baltoli Baltoli force-pushed the bind-raw-term-strip branch from 05c9709 to 23e9e5e Compare November 28, 2023 21:19
@Baltoli Baltoli marked this pull request as ready for review November 28, 2023 21:20
Copy link
Contributor

@tothtamas28 tothtamas28 left a comment

Choose a reason for hiding this comment

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

Python part looks good.

Test in pyk: runtimeverification/pyk#748

rv-jenkins pushed a commit that referenced this pull request Dec 1, 2023
Part of: #905

In #905, we are implementing a Python binding for the backend's function
evaluator: given a function label and list of argument `Pattern`s,
construct runtime terms for the arguments, evaluate the function with
the given label, and return the result as an AST pattern.

To safely reify the runtime term produced by the function call to an AST
pattern, we need to know its sort (so that the machinery in #907, #908
can be used correctly). In some places in the bindings, we have to
require that callers provide a sort when reifying terms back to
patterns. However, when calling a function, the label of the function
determines precisely the correct sort to use.

This PR emits a new table of global data into compiled interpreters that
maps tags to declared return sorts, along with a function that abstracts
away indexing into this table. This change is similar to (but simpler
than) an existing table of _argument sorts_ for each symbol that we
already emit.

Testing is handled by binding the new function to Python.
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.

Assuming that the changes on the function signatures don't break anything on pyk and on python's bindings, The c++ part LGTM!

@rv-jenkins rv-jenkins merged commit 04dd60e into master Dec 5, 2023
@rv-jenkins rv-jenkins deleted the bind-raw-term-strip branch December 5, 2023 15:25
rv-jenkins pushed a commit to runtimeverification/pyk that referenced this pull request Dec 6, 2023
rv-jenkins pushed a commit that referenced this pull request Dec 18, 2023
This PR adds a new feature to the backend's binding API that allows for
function symbols to be evaluated on a set of AST pattern arguments, with
the result returned as a pattern also. This is motivated by the proof
generation project; the execution trace format generated by the backend
to summarise a concrete execution can contain the labels and arguments
for function call events, but not the functions' return values without
breaking tail-call optimisation.

Most of the prerequisite work for this PR was done in #908 and #911; the
actual changes here are quite small:
* Adds a sort-aware term-to-pattern reification method that uses the new
`rawTerm{}` wrapper.
* Marshals arguments and returns between pattern and term level in the
core bindings API.
* Adds a test case demonstrating a few simple cases for this feature; as
ever the bulk of the testing ought to be performed in Pyk.
Baltoli pushed a commit to runtimeverification/k that referenced this pull request Apr 9, 2024
Baltoli pushed a commit to runtimeverification/k that referenced this pull request Apr 9, 2024
Baltoli pushed a commit to runtimeverification/k that referenced this pull request Apr 9, 2024
Baltoli pushed a commit to runtimeverification/k that referenced this pull request Apr 10, 2024
Baltoli pushed a commit to runtimeverification/k that referenced this pull request Apr 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants