You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
The text was updated successfully, but these errors were encountered: