-
Notifications
You must be signed in to change notification settings - Fork 63
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
Cryptol primitives can't be made uninterpreted #1044
Comments
My first attempt at this was to change the Perhaps a better, less disruptive approach would simply be to rename all the constants in |
I have a patch for renaming some of the primitives in |
When this ticket is closed, we should also add the |
@brianhuffman, do you have idea/plans for this issue? I think #347 is now also basically an instance of this issue. |
Yes: My plan is to rename all the functions in |
Just now I was trying to do a proof involving Cryptol's |
Usually constants translated from Cryptol are eligible to be made uninterpreted with tactics like
unint_z3
. But it doesn't work if the constant is a cryptol primitive. For example:The deeper problem is that the name "
complement
" is not registered under its proper name in saw-core, as other cryptol constants are. If we print the term, we can see that there is no trace of the original name:The text was updated successfully, but these errors were encountered: