Document that GLPK/exact can be inexact #35773
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
📚 Description
The GLPK/exact linear programming (LP) backend isn't exact because rationals are converted to doubles to be passed to the backend. This means that, despite solving LPs exactly over the rationals, the solver can silently solve a rounded version of your LP. For example, coefficients of 1/3 are handled incorrectly as they are rounded to some 0.3333333ish number that fits in a double-precision float.
This PR simply expands the relevant documentation to explain more carefully that this can lead to problems. Fixes #35727.
The modified files lie in the
src/
subdirectory, are changes required to files with the same relative path under such as/build/pkgs/sagemath_environment/...
,build/pkgs/sagemath_repl/...
, andpkgs/sagemath-repl/...
?📝 Checklist
⌛ Dependencies