Guido Tack

The output is required to be type correct with respect to the variable definitions. If your MiniZinc model has a variable `var float: x;` then an assignment item like `x...

I pushed a fix but I'm not 100% sure it's for the issue you're reporting. The fix addresses the problem that the following code didn't work: ``` var set of...

This is more likely to be the final cleanup of the garbage collector, which can take several seconds for large models. I'm working on a fix for this.

I agree this would be nice. However it requires full incremental type checking of the model, and the type checking would have to be reasonably robust against syntax and type...

Thanks a lot for your work on this! I think we'll need to reorganise the repositories a bit before merging this one. Currently this repo has a dual role: as...

This is a feature that is (was) available in the full Zinc language in a restricted form, which supports constrained types like this: `type NonNegFloat = (float: x where x...

The problem here is that removing the surrounding `if` has a different meaning: ``` A[t,r,c] = if false then false else A[t-1,r,c] \/ A[t,r-1,c] \/ A[t,r+1,c] \/ A[t,r,c-1] \/ A[t,r,c+1]...

Unfortunately this code is triggering a heuristic in the compiler that tries to aggregate disjunctions, which become longer and longer here. We'll need to come up with a tweak to...

Thanks for the contribution, this is something I'd like to incorporate. At the moment, it looks like the solver can either accept stdin or a file, right? I would prefer...

This is a current limitation in the type inference algorithm. Unfortunately there is no direct workaround, except using code like ``` array[1..3] of var bool: x; ``` Changing this will...