-
Notifications
You must be signed in to change notification settings - Fork 0
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
Address Code Review Issues #37
base: spec/feature/bls-dependencies
Are you sure you want to change the base?
Address Code Review Issues #37
Commits on Oct 3, 2024
-
blshelpers: Replace list comprehension with map in compute_powers
Just out of preference, since it makes it clear we are just mapping a conversion over all the elements in the powers' list.
Configuration menu - View commit details
-
Copy full SHA for df3b8be - Browse repository at this point
Copy the full SHA df3b8beView commit details -
blsserde: Remove polymorphic type n from get_flags
And hardcode to work on a 384-bit value. I'm doing this for two reasons: first, because it better matches the Python spec; second, because it will only ever be used a 384-bit value, so there is no need for it to be more abstract; and third, because it reduces complexity making the function be monomorphic.
Configuration menu - View commit details
-
Copy full SHA for 83ee134 - Browse repository at this point
Copy the full SHA 83ee134View commit details -
blsserde: Replace call to int_to_bit with builtin indexing operator
Previously, I got the LSB by calling the custom int_to_bit function, but this can be done by indexing the zero-ith bit from the back, using '!0'.
Configuration menu - View commit details
-
Copy full SHA for 564f347 - Browse repository at this point
Copy the full SHA 564f347View commit details -
utils: Remove unused function int_to_bit
Since it was no longer used and there is a builtin way to get the LSB.
Configuration menu - View commit details
-
Copy full SHA for 155acc6 - Browse repository at this point
Copy the full SHA 155acc6View commit details -
blshelpers: Clarify differences between g1_multi_exp and multi_exp
The Python spec function multi_exp handles both G1 and G2 points. Our g1_multi_exp is hardcoded to G1 points.
Configuration menu - View commit details
-
Copy full SHA for 1fd9595 - Browse repository at this point
Copy the full SHA 1fd9595View commit details -
blsserde: Use | in place of nested if else
Preference for readability and to imply case matching.
Configuration menu - View commit details
-
Copy full SHA for 6e2a0cf - Browse repository at this point
Copy the full SHA 6e2a0cfView commit details -
blsserde: Add missing check for point at infinity from compressed value
In the decompress_G1 function. We now match the Python spec.
Configuration menu - View commit details
-
Copy full SHA for d7d6bbe - Browse repository at this point
Copy the full SHA d7d6bbeView commit details