-
Notifications
You must be signed in to change notification settings - Fork 83
Differing outputs when FlatZinc code is passed via stdin vs. file #655
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
The difference between the two commands is that when using In a MiniZinc model, FlatZinc annotations ( As far as I know, there is currently no input from stdin that would allow you to pass in FlatZinc (as FlatZinc) to the compiler. However, some solvers do allow this. |
I believe there is an argument |
Thanks a lot! If appreciated I'd like to add |
Feel free to send a pull request. The |
When running the following FlatZinc file
minimal.fzn
:with
cat minimal.fzn | minizinc --input-from-stdin --solver Chuffed
(or gecode) the output only prints the int vars:but when running
minizinc --solver Chuffed minimal.fzn
(or gecode) the output also correctly outputs the variable array:I am not (yet) familiar enough with the libminizinc code base to make any educated guess, where this might come from, or whether this is user error, but I think both should output the array.
The text was updated successfully, but these errors were encountered: