Fix usage of BigInteger in DiscordBitSet.value
#864
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.
DiscordBitSetcan only represent positive numbers, so theBigIntegerused for getting a decimal representation can be constructed using the sign-magnitude representation instead of the two's-complement binary representation.This fixes two bugs:
DiscordBitSets with an emptydataarray couldn't be converted to aBigIntegerbecause the constructor taking the two's-complement binary representation throws aNumberFormatExceptionif the given array is empty.This bug was reported by @Tmpod: https://discord.com/channels/556525343595298817/1147254164469063773
DiscordBitSetswith a negativeLongat the last position in theirdataarray would be misinterpreted as negative numbers in the conversion toBigIntegers because the two's-complement binary representation was used.Example where this bug could be observed: