-
Notifications
You must be signed in to change notification settings - Fork 479
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
Kwxm/bls12 381/minor fixes #5367
Conversation
@@ -274,7 +276,7 @@ groth16Verify | |||
:: BuiltinByteString -- G1 | |||
-> BuiltinByteString -- G2 | |||
-> BuiltinByteString -- G2 | |||
-> BuiltinByteString -- G1 | |||
-> BuiltinByteString -- G2 |
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.
Seems like it might be worth having some newtype
s here idk?
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.
Yeah, I was a bit confused when I looked at that today. These types are wrapped in newtypes
elsewhere in this file, but not here. I think I did that because what we're really wanting to measure here is what happens on the chain, and having newtypes here would cost a little more. I think we get delay
or something in the uplc if we do that, which I was slightly surprised by when I found out. I could be wrong about that though: I'll check.
instance ExMemoryUsage BLS12_381.Pairing.MlResult where | ||
memoryUsage _ = singletonRose . unsafeToSatInt $ BLS12_381.Pairing.mlResultMemSizeBytes `div` 8 | ||
memoryUsage _ = mlResultElementCost |
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.
The stuff above is in response to this comment from @effectfully .
This is just responding to a couple of small things raised in the PR comments; the main branch got merged while I was fixing these.