Fix multiple applicable rules for Minion #405
Labels
area::minion
Related to minion_rs, the minion C++ bindings, and the minion solver interface.
kind::bug
Something isn't working
priority::next
We need this next.
Sometimes, there are multiple applicable rules in tests. In #401 , we add a check for this, which causes test failures.
We only should have one representation of the model at the moment (per solver, at-least), and I am writing my Minion rules with a set order of operations in mind. These failing rules likely either have a bad priority, or don't have strict enough preconditions.
The text was updated successfully, but these errors were encountered: