Allow different parsing strategies #4205
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
|
|
@NikolajBjorner may you help me why the Build CI tasks all fail? |
Your code is not type correct. |
|
Thanks @NikolajBjorner I'll add the remaining functions in the next PR :) |
hgvk94
pushed a commit
to hgvk94/z3
that referenced
this pull request
May 7, 2020
* modifiers * modifiers and function * revert * .
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
the java API only allows parsing Strings to Arrays of BoolExpr, but the ASTVector can also parse to other types like, IntExpr, RealExpr etc.
To allow that those constructors and funtion nCtx() need to be public