Jip J. Dekker

Although I do think that it would be a good idea to release a new version of Gecode, it should be noted that in the develop version of MiniZinc the...

Currently MiniZinc Python is not designed for FindMUS usage. FindMUS is a very different from a normal MiniZinc solver (and MiniZinc Python has really been designed for solving MiniZinc instances)....

That sounds great! We'll have to have a discussion in the MiniZinc team how we want to handle these kinds of solvers and in particular the output of MUS/IIS (which...

Hi Stephe, Although this is certainly a valid workaround, it does seem like the workaround would needlessly complicate the grammar (compared to having a DSL construct). To me it feel...

The `verbose` and `debug_output` arguments have been included mostly for finding problems when MiniZinc Python wasn't giving users the expected behaviour. It was not intended for polling the solver progress....

I suspect that this is an issue with the internal Gecode interface that occurs when part of the input of an `all_different` constraint is already fixed. The version of Gecode...

The problem is resolved when you select the “edge” version of MiniZinc in the playground. The fix has not been included in any release yet, so the “latest” version does...

I'm afraid that, although we should probably improve the error message, this is just a limitation in MiniZinc. The compiler does not support `set of string` objects. Please have a...

Although you are right that the solver output can contain something like `X = 1.1..3.3` according to the syntax spec, this does not guarantee that using a range as a...

It should be allowed if the variable was actually a set type: ``` var set of 1.0..10.0: x; ``` In this case assigning `x = 1.0..3.0` would be type correct....