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
With the latest update of MiniZinc to version 2.9.0 the implicit conversion of enums to ints emits a warning with the requirement that the user makes the conversion explicit using enum2int. Currently, in the IDE the warnings do not contain file/line-number/column information (as is typical for errors), although it is available when minizinc is run from the command-line. I have also tried using -Werror, to convert the warnings to errors, but it does not change the output in the IDE. When compilation errors arise in the IDE, the user can find the location of where the changes need to be made directly by clicking on the provided link to the file in the output window, facilitating the process of systematically fixing errors. As such, it would be helpful if
(1) warnings also emit the file/line-number/column information in the output window from where it can be found in the mzn files for fixing and
(2) the user can add a command-line parameter that tells MiniZinc to emit all warnings rather than stopping after a few.
The text was updated successfully, but these errors were encountered:
Thanks! The issue with warning locations not being shown in the IDE will be fixed in the next release (or you can use the edge release to test out the fix now).
With the latest update of MiniZinc to version 2.9.0 the implicit conversion of enums to ints emits a warning with the requirement that the user makes the conversion explicit using enum2int. Currently, in the IDE the warnings do not contain file/line-number/column information (as is typical for errors), although it is available when minizinc is run from the command-line. I have also tried using -Werror, to convert the warnings to errors, but it does not change the output in the IDE. When compilation errors arise in the IDE, the user can find the location of where the changes need to be made directly by clicking on the provided link to the file in the output window, facilitating the process of systematically fixing errors. As such, it would be helpful if
(1) warnings also emit the file/line-number/column information in the output window from where it can be found in the mzn files for fixing and
(2) the user can add a command-line parameter that tells MiniZinc to emit all warnings rather than stopping after a few.
The text was updated successfully, but these errors were encountered: