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

Clean up MulByXXX methods, hard-coded non-residue constants in the template generator #10

Merged
merged 23 commits into from
Jul 10, 2020

Conversation

ggutoski
Copy link
Contributor

@ggutoski ggutoski commented Jul 9, 2020

Solves #7 , #8 .
All the hard-coded constants mentioned in #8 appear only in the MulByXXX methods in pairing.go for each curve. It was decided that pairing code will not be generated from template (see #9 ). As such, I've simply removed code for generating twoInv from the template generator.

…plate fpInlineMulByNonResidue, clean up generated comments
…template fpInlineMulByNonResidueInv, more comment cleaning
…template fp2InlineMulByNonResidueInv, clean up some dollar signs
…good thing no one called this code; good thing we had tests... :rolleyes:
…o to pairing.go, delete MulByV2NRInv, MulByNWNRInv, MulByWNRInv
…k commit 7dcd496ba42799bf1d4b695226ce6cc4c1f48792
@ThomasPiellard ThomasPiellard merged commit 8072f19 into develop Jul 10, 2020
@ggutoski ggutoski deleted the refactor-constants branch July 14, 2020 14:29
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 this pull request may close these issues.

2 participants