[4.10.2] [minor] "At least one constraint is free, i.e., neither posted or reified. )." while constraint.getOpposite() is posted.

[glelouet]

The code that generates this is :

		Model choco = new Model();
		IntVar a = choco.intVar(1,2);
		Constraint expr = choco.arithm(a, "<", 2);
		BoolVar f = choco.boolVar(false);
		expr.reifyWith(f);
		choco.getSolver().solve();

I diged a bit, it seems to be the constraint.reifyWith(bv) call that generates this warning.

		Model choco = new Model();
		Constraint expr = choco.arithm(choco.intVar(1, 2), "<", 2);
		expr.getOpposite().post();
		choco.getSolver().solve();

IMO that can be fixed in Constraint#getStatus(), l313 :
- return mStatus;
+ return (mStatus==FREE && opposite!=null)?opposite.mStatus:mStatus;

unit/noregression test :

		Model choco = new Model();
		Constraint expr = choco.arithm(choco.intVar(1, 2), "<", 2);
		expr.getOpposite().post();
		assert expr.getStatus() == Status.POSTED;

[cprudhom]

I bet this is already fixed in 4.10.3 (see 640461e)

[glelouet]

That fix is bad. c.getOpposite() will always enforce the opposite is not null.
I checked if there was a test possible for c.hasOpposite() and there was none, that's why I propose to modify the getStatus() instead, which incidentally reduces the possibility of a bug for the same reasons.

[glelouet]

@cprudhom please reopen. The fix is bad.

[cprudhom]

My bad, your test should not thrown the message.
The getStatus() should consider the opposite too.