Remove error conditions from Largest-First. #76
Merged
Conversation
This file contains 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
The current design of Largest-First makes it impossible for these error conditions to occur. We therefore remove them from the documentation.
paweljakubas
approved these changes
May 12, 2020
jonathanknowles
deleted the
jonathanknowles/remove-impossible-error-conditions
branch
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.
Related Issue
#75
Summary
Recent changes to the design of
Largest-Firstmean that it is now impossible for the algorithm to encounter the following two error conditions:InputCountInsufficientErrorInputsExhaustedErrorThis change removes these error conditions from the documentation for
Largest-First.