-
Notifications
You must be signed in to change notification settings - Fork 62
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
Uninformative error message for uninterpreted polymorphic functions #320
Comments
I just checked, and this is still a problem. Here's how to easily reproduce the error:
What we want is for this example to just work. When we ask for a polymorphic function to be uninterpreted, the SMT-Lib backend should get a separate uninterpreted function declared at each type instance that the function is used at. |
This works by declaring monomorphic uninterpreted functions at each type instance, using a name suffix based on the type value. Fixes GaloisInc/saw-script#320.
This works by declaring monomorphic uninterpreted functions at each type instance, using a name suffix based on the type value. Fixes GaloisInc/saw-script#320.
I'm reopening for now, until we add a proper regression test to the saw-script test suite. |
I was trying a proof using
unint_yices
and encountered this error messageThe actual problem, as I eventually found out, is that I had asked for a polymorphic function to be uninterpreted. This error message is not much help in figuring that out!
The text was updated successfully, but these errors were encountered: