You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
One variable with long long int domain. One constraint. Very very long compile time. #210
This is due to a limitation in the current FlatZinc text format, which cannot represent domains with holes very well. For this example, it will have to create a text file that lists all the possible domain values, rather than something like this:
var range_list([-536870912..-1,1..536870912]): helloworld_str2_cpu_id;
We don't have a workaround for this bug at the moment. Solvers that are directly interfacing to MiniZinc don't run into this issue (e.g. the MIP solvers). We are planning to introduce range list syntax for FlatZinc in a future release.
Activity
zayenz commentedon Jan 15, 2025
Are you compiling with -O5? That mode is dependent on the size of the domains.
DannyGeist commentedon Jan 15, 2025
No. -O5 is slow on big mzn models
guidotack commentedon Mar 5, 2025
This is due to a limitation in the current FlatZinc text format, which cannot represent domains with holes very well. For this example, it will have to create a text file that lists all the possible domain values, rather than something like this:
We don't have a workaround for this bug at the moment. Solvers that are directly interfacing to MiniZinc don't run into this issue (e.g. the MIP solvers). We are planning to introduce range list syntax for FlatZinc in a future release.