-
Notifications
You must be signed in to change notification settings - Fork 233
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
BSI library expanded to include support for large arbitrary values via the big.Int library #451
Conversation
@guymolinari Can you have a look at our failing tests? |
Looking.....
…On Wed, Oct 23, 2024 at 12:33 PM Daniel Lemire ***@***.***> wrote:
@guymolinari <https://github.com/guymolinari> Can you have a look at our
failing tests?
—
Reply to this email directly, view it on GitHub
<#451 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ADZZAUVZ45INXI6QGBMBA23Z47TYTAVCNFSM6AAAAABQPMBCZOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMZTGEZTCOJSGI>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Daniel. Would it be possible to update the environment to use at least go 1.15? |
Absolutely. Maybe it would be cleaner to do it with a separate PR. We could push the required version up, and then handle this PR. |
Daniel. Missed your last message. I think I have it sorted out now. |
Let us merge. |
There is no fundamental reason why the BSI library cannot support values exceeding 64 bits. Why is this necessary? It would now be possible to store values like UUID and 96 bit timestamps, as well as advanced string encodings in a BSI.
The BSI library has been modified to preserve the existing int64 interface and has been expanded to leverage the golang big.Int math library. The original int64 methods now convert incoming values to *big.Int (and vice versa, etc).
Additional test coverage has been added and some of the original tests have been expanded.
Performance does not seem to be substantially impacted.