Currently still_feasible does a soft check which fails when called from an indicator or reified constraint.
i.e the inner constraint can be violated if not activated. When setting a new value it seems like it can work i.e the all different constraint only checks if that number exists already.
Makes sense to a is_constraint_violated function which does a hard check.
Currently
still_feasibledoes a soft check which fails when called from an indicator or reified constraint. i.e the inner constraint can be violated if not activated. When setting a new value it seems like it can work i.e the all different constraint only checks if that number exists already.Makes sense to a
is_constraint_violatedfunction which does a hard check.