-
Notifications
You must be signed in to change notification settings - Fork 2
Exporting get_requires
utils function
#1056
Conversation
This is a requirement from the Math Proof Generation Team of $Piˆ2$ to get easy access to the Pattern of a requires clause. This PR must be merged before this [PyK PR](runtimeverification/pyk#1056) that will properly expose this binding to the Pi2 project.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please add a unit test for this feature. That will also block merging this PR until the binding becomes available.
Hasn't there been a plan to eventually implement it in |
That was revisited, and we decided to move in another direction to avoid having the exact implementation in two different places when we could just export them. |
I've just added a unit test, and I'm waiting for this PR to be approved |
e9cbe24
to
ca02a8b
Compare
This PR introduces a new file, `utils.py`, which should contain auxiliary functions that need to be converted from and to llvm but don't set any field on an object. In this context we're using a function from llvm backend's [pattern_matching.cpp](https://github.com/runtimeverification/llvm-backend/blob/e2f583a05b9bf362deabd58f8acc1ce534aaf4c4/lib/ast/pattern_matching.cpp#L174) to avoid reimplement it in Python. This function is exported as Pyhton binding in this [PR](runtimeverification/llvm-backend#1019), and therefore, the current PR can only be merged after we merge the LLVM Backend one. --------- Co-authored-by: devops <[email protected]>
This PR introduces a new file, `utils.py`, which should contain auxiliary functions that need to be converted from and to llvm but don't set any field on an object. In this context we're using a function from llvm backend's [pattern_matching.cpp](https://github.com/runtimeverification/llvm-backend/blob/e2f583a05b9bf362deabd58f8acc1ce534aaf4c4/lib/ast/pattern_matching.cpp#L174) to avoid reimplement it in Python. This function is exported as Pyhton binding in this [PR](runtimeverification/llvm-backend#1019), and therefore, the current PR can only be merged after we merge the LLVM Backend one. --------- Co-authored-by: devops <[email protected]>
This PR introduces a new file, `utils.py`, which should contain auxiliary functions that need to be converted from and to llvm but don't set any field on an object. In this context we're using a function from llvm backend's [pattern_matching.cpp](https://github.com/runtimeverification/llvm-backend/blob/e2f583a05b9bf362deabd58f8acc1ce534aaf4c4/lib/ast/pattern_matching.cpp#L174) to avoid reimplement it in Python. This function is exported as Pyhton binding in this [PR](runtimeverification/llvm-backend#1019), and therefore, the current PR can only be merged after we merge the LLVM Backend one. --------- Co-authored-by: devops <[email protected]>
This PR introduces a new file, `utils.py`, which should contain auxiliary functions that need to be converted from and to llvm but don't set any field on an object. In this context we're using a function from llvm backend's [pattern_matching.cpp](https://github.com/runtimeverification/llvm-backend/blob/e2f583a05b9bf362deabd58f8acc1ce534aaf4c4/lib/ast/pattern_matching.cpp#L174) to avoid reimplement it in Python. This function is exported as Pyhton binding in this [PR](runtimeverification/llvm-backend#1019), and therefore, the current PR can only be merged after we merge the LLVM Backend one. --------- Co-authored-by: devops <[email protected]>
This PR introduces a new file,
utils.py
, which should contain auxiliary functions that need to be converted from and to llvm but don't set any field on an object.In this context we're using a function from llvm backend's pattern_matching.cpp to avoid reimplement it in Python. This function is exported as Pyhton binding in this PR, and therefore, the current PR can only be merged after we merge the LLVM Backend one.