Skip to content

minizinc 2.5.0 does not use fzn_alldifferent_except_0 #414

Closed

Description

@informarte

Past versions of minizinc translated alldifferent_except_0 to fzn_alldifferent_except_0 which several solvers implement. The constraint library of minizinc 2.5.0, however, translates alldifferent_except_0 to fzn_alldifferent_except, bypassing any definition of fzn_alldifferent_except_0.

Is this change intentional or accidental? (It was introduced by fd57ce5.)

In order to keep the improved default decomposition of alldifferent_except_0 and, at the same time, to allow for solver-specific definitions of fzn_alldifferent_except_0, I suggest to revert the change to the definition of alldifferent_except_0 and to translate fzn_alldifferent_except_0 to fzn_alldifferent_except.

Activity

  1. added a commit that references this issue on Oct 11, 2020
    c7a0ebf
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions