Skip to content
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

BigInt_from_hex_string requires its parameter to have full words #5

Open
wjmelements opened this issue Nov 7, 2024 · 0 comments
Open

Comments

@wjmelements
Copy link

For a word size of 8, I would expect BigInt_from_hex_string(2, result, "abcdefABCDEF0123456789" to make [abcdef, abcdef0123456789]; instead it makes [0,abcdef0123456789]. It works if you pass "0000000000abcdefABCDEF0123456789".

This is consistent with the behavior of BigInt_to_hex_string though, which pads zeroes.

My main complaint is that I would expect the parsing function to not require its parameters to be padded to the word size. I don't use this function much outside testing though, so it's not too important for my use case.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant