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

Reverse order of Concat/Split arguments? #519

Closed
tarcieri opened this issue Dec 27, 2023 · 0 comments · Fixed by #526
Closed

Reverse order of Concat/Split arguments? #519

tarcieri opened this issue Dec 27, 2023 · 0 comments · Fixed by #526

Comments

@tarcieri
Copy link
Member

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.

tarcieri added a commit that referenced this issue Dec 27, 2023
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
tarcieri added a commit that referenced this issue Dec 28, 2023
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
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

Successfully merging a pull request may close this issue.

1 participant