Implemented error when incorrect bounds cause discrete_log to give incorrect answer #39484
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.
Fixes #38316 .
When the bounds provided to the discrete_log function did not contain the correct answer the function would sometimes return an incorrect answer.
This was fixed by adding the parameter 'check' to the function. This parameter is True by default. If 'check' is True then the function verifies the answer, returning it if it is correct and throwing a Value Error if it is not. If 'check' is False then the function returns the (possibly incorrect) answer without verifying it.
A doctest was added to verify that the function correctly throws an error in a situation where it previously returned an incorrect answer.
📝 Checklist
⌛ Dependencies