-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Have Z3_set_param_value indicate if a setting is being ignored #7100
Comments
dump_models is defined two places:
It means different things for the two uses.
They happen to have the same name, but may as well have been renamed apart. |
If this is Z3_Context in the C API, then setting If helpful, I could try writing a C program that shows this behavior. |
Alright, dump_models is only intended to be used from the text API. |
Z3_set_param_value
seems to ignore global parameters, for whichZ3_global_param_set
should be set. Unfortunately, this is not obvious to users when they interact with Z3 through another layer (like smtlib-backends).Would it be possible to query the API to learn if some parameter set with
Z3_set_param_value
has been ignored? This would allow to give users an explicit error message when things don't go as expected.This issue surfaced when a user was trying to start a Z3 context with
dump_models
set totrue
.Another solution could be having a way to test whether a parameter is in the domain of
Z3_set_param_value
ahead of making the call. There is a callZ3_get_global_param_descrs
, but it requires having a Z3 context first, which isn't necessary withZ3_set_param_value
.The text was updated successfully, but these errors were encountered: