clpfd: unexpected failure

Open UWN opened this issue 4 years ago • 4 comments

| ?-      fd_domain([A],0,1),A#==>0#>0/0.

no            % unexpected
| ?- A=0, fd_domain([A],0,1),A#==>0#>0/0.

A = 0         % expected

Related to #86.

Aug 09 '21 08:08 UWN

Just a general remark: I do not test GNU any further for its clpfd-extension as this issue here is not fixed.

Mar 15 '22 10:03 UWN

I understand but this case is rather difficult to fix in practice in the general case (this is a particular case only). Maybe raise an error when 0/0 appears (even in 0#==>0/0)...

Mar 16 '22 08:03 didoudiaz

An error for 0/0 does not make sense. Other systems just fixed this as SICStus withdrew 4.3.4, and SWI (at that time) alike.

Mar 16 '22 09:03 UWN

UWN_blocking

Oct 04 '22 04:10 UWN