You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
ExactSumConstraint implicitly assumes the inputs are non-negative and optimizes internally for that assumption. I didn't write it, but my guess is that finding exact sums from sets of non-negative numbers fits a certain problem domain, and this was intended for that.
It might be better to update the documentation for ExactSumConstraint than to change its behavior, and @ltskinol could write a separate constraint class for their problem domain.
This seems like the ExactSumConstraint doesn't behave as can be expected from the name. I don't have the time to look into it, if someone else could that would be great.
Shouldn't a==-1, b==1 and a==1, b==-1 also be solutions?
Thanks.
The text was updated successfully, but these errors were encountered: