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

Add python bindings for proof hint streaming parser #1075

Merged
merged 7 commits into from
Jun 3, 2024

Conversation

dwightguth
Copy link
Collaborator

Previously we did not have any python bindings for the streaming parser I created.

This PR adds the relevant pybind code as well as adding a python unit test for that code. A slight change is made to the ownership semantics of proof_trace_buffer and its derived classes in order to allow the python bindings to work as expected.

@rv-jenkins rv-jenkins changed the base branch from master to develop May 31, 2024 17:01
@dwightguth dwightguth marked this pull request as ready for review May 31, 2024 17:57
Copy link
Collaborator

@theo25 theo25 left a comment

Choose a reason for hiding this comment

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

Looks good to me. I left two minor comments

tools/kore-proof-trace/main.cpp Outdated Show resolved Hide resolved
bindings/python/ast.cpp Outdated Show resolved Hide resolved
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. I would like to see a follow-up PR adding these new bindings in prooftrace.py with appropriate in-line documentation following our current pattern to expose the hints bindings to the Math Proof Generation Team!

@rv-jenkins rv-jenkins merged commit f2bbc3d into develop Jun 3, 2024
10 checks passed
@rv-jenkins rv-jenkins deleted the parser-python branch June 3, 2024 20:02
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.

5 participants