Jeshan Giovanni BABOOA

Fixes #27 _Please review as I do make mistakes sometimes!_ https://github.com/mthom/scryer-prolog/pull/420

Unification may fail with user attributes

4

I've found that we have a situation where unification could fail if a custom attribute is added before a clpz constraint is posted. Consider this code ```prolog :- use_module(library(atts)). :-...

Update custom constraint example

3

Syntax usage was outdated (since clpfd days). It took me quite some head scratcing to realise that `run_propagator` extensions should be a dcg rule nowadays!

I got a few requests for Visual Studio Code on reddit. The docs: https://code.visualstudio.com/docs/editor/userdefinedsnippets Example github project that provides snippets: https://github.com/johnpapa/vscode-angular-snippets To demonstrate interest in and prioritise this, click the...

Dictionary parameters does not seem to work

1

Declaring my parameters with `dict`, I was expecting the `dictionaries` strategy to work out of the box but it does not seem to be so. I was only seeing `{}`...

Source: https://github.com/crytic/evm-opcodes#table

#= may fail in one direction but not the other

4

I've found a case where `A#=B` fails while `B#=A` does not. The issue is more readily observed with a custom propagator: ```prolog :- use_module(library(clpz)). :- multifile clpz:run_propagator/4. try :- A+B...

min could settle if one input and the other's upper bound are known

1

I'm wondering if we could we unify `B=A` here: ```prolog A in 0..100, B #= min(100, A). ``` returns: ``` clpz:(B#=min(100,A)), clpz:(A#>=B), clpz:(A in 0..100), clpz:(B in 0..100) ? yes...

Please verify