Repository navigation
"low" changed to "lowElement", "high" changed to "highElement" - #46
Merged
Merged
Conversation
Updated binary search implementation to fix termination issues by changing variable names and adjusting the decreases condition for loop termination checking.
Refactor BinarySearchOverflow to prevent integer overflow during mid calculation by using lowElement and highElement.
Collaborator
|
Hi Kwok, thank you for the PR, it is much appreciated :) |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The keyword “low” in Gobra denotes low security in the non-interference model. Therefore, if “low” is defined as a variable, Gobra will produce the following compilation error due to a presumed keyword clash:
The best approach is to rename "low" to "lowElement" and "high" to "highElement". I left "mid" unchanged, since it is already unambiguous :)