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
This crate uses a little endian limb ordering, with the least significant limbs first and the most significant last.
#34 reversed return tuples for functions like mul_wide to return (lo, hi) rather than (hi, lo). However, Concat(Mixed) and Split still use a hi/lo ordering.
I would suggest reversing this for consistency, so the ordering is consistent with the ordering of the limbs themselves.
The text was updated successfully, but these errors were encountered:
Changes to a "little endian" `lo, hi` convention for the ordering of
arguments to concatenation methods and the ordering of the returned
2-tuple from split methods.
This is more consistent with the rest of the crate, and the
`Uint { limbs }` which uses a little endian ordering.
Closes#519
Changes to a "little endian" `lo, hi` convention for the ordering of
arguments to concatenation methods and the ordering of the returned
2-tuple from split methods.
This is more consistent with the rest of the crate, and the
`Uint { limbs }` array which uses a little endian ordering.
Closes#519
This crate uses a little endian limb ordering, with the least significant limbs first and the most significant last.
#34 reversed return tuples for functions like
mul_wide
to return(lo, hi)
rather than(hi, lo)
. However,Concat(Mixed)
andSplit
still use a hi/lo ordering.I would suggest reversing this for consistency, so the ordering is consistent with the ordering of the limbs themselves.
The text was updated successfully, but these errors were encountered: