-
Notifications
You must be signed in to change notification settings - Fork 162
Group Order() function signature oddity #214
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
Comments
About returning big.Int: I think returning this type motivates users to perform scalar operations using big.Int, which is not desirable, instead we are already providing Scalar arithmetic operations. I think the |
I think you may have misunderstood the comment. In the example snippet you wrote -- |
I do agree with @armfazh that |
That's fair. I think a reasonable thing to do here is to just remove this function from the interface altogether. It's not needed. |
@bwesterb points out that this prototype is somewhat strange:
Since Scalars are integers between 0 and q-1, the output of this function should be zero! Perhaps this just needs to be a
big.Int
, instead?@armfazh, what do you think?
The text was updated successfully, but these errors were encountered: