minion_rs / minion_c++: internal Minion checks throw SIGTERM; we probably want an exception instead? #244
Labels
area::minion
Related to minion_rs, the minion C++ bindings, and the minion solver interface.
kind::bug
Something isn't working
kind::feature
New feature or request
Milestone
When testing #230, Felix and I mistakenly used a watchneq constraint with bound variables. This triggered, during search, an internal minion check that SIGTERM-ed the entire executing process:
I think it would be useful for these to throw an exception over FFI instead of terminating the program. An immediate use-case for this would be improperly type-checked constraints inside our cargo tests : currently, the failing test SIGTERMs the entire test suite whereas an exception would be passed upwards and reported as a test failure.
The text was updated successfully, but these errors were encountered: