-
Notifications
You must be signed in to change notification settings - Fork 12
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
General improvements #56
Conversation
/// The protocol has failed and can't be completed. | ||
Protocol, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I couldn't come up with a better name or description that actually explains the error to a user. I think InverseError
doesn't make any sense to a user.
d0ccc11
to
95fd303
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good overall, will merge!
Oh oops, I probably should have re-run the CI before merging this, seems like the main branch now is failing CI. @daxpedda any ideas here? |
Yes ... this is interesting and something I wasn't aware of, depending on pre-releases can automatically update. I thought that pre-releases can not update as they are considered unstable. This is addressed by #54, I'm gonna pin pre-release dependencies there. |
Builds on #55.
Ristretto255
.NonVerifiableServerEvaluateResult
as it was holding only one type.warn(missing_debug_implementations)
and implementDebug
on all public types.copy
methods now that we are compiling withoutalloc
.PreparedEvaluationElement
andPreparedTscalar
.Iterator
s in the public API.Evaluate
according to the spec.GenericArray
s to slices.new_with_key
would panic if bytes don't have the right length.serde
de/serialization to use the checked variants inGroup
.