FlagsConverter tweaks & code cleanup
#122
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
…of the flag Finding the smallest flag combination that completely encompasses a given value is actually NP-hard. See: https://en.wikipedia.org/wiki/Set_cover_problem What we use here is a greedy O(N²) algorithm but the biggest integer is 64 bits so the worst case doesn't seem that bad.
desjarlais
approved these changes
May 13, 2024
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.
Changes of insterest:
FlagsConverterso it produces smaller string representations of the flagFinding the smallest flag combination that completely encompasses a given value is actually NP-hard. See: https://en.wikipedia.org/wiki/Set_cover_problem
What we use here is a greedy O(N²) algorithm but the biggest integer is 64 bits so the worst case doesn't seem that bad.