-
Notifications
You must be signed in to change notification settings - Fork 483
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
[Builtins] Add an inlinable version of 'GEq' #4462
Conversation
d40f4bc
to
8c0fbe1
Compare
/benchmark plutus-benchmark:validation |
Comparing benchmark results of 'plutus-benchmark:validation' on 'edcf0e886' (base) and '8c0fbe11d' (PR)
|
/benchmark plutus-benchmark:validation |
Comparing benchmark results of 'plutus-benchmark:validation' on 'edcf0e886' (base) and 'b06b651dc' (PR)
|
b06b651
to
5a3e025
Compare
/benchmark plutus-benchmark:validation |
Comparing benchmark results of 'plutus-benchmark:validation' on 'dc9275462' (base) and '5a3e025a2' (PR)
|
-1.24% on average. Not a huge speedup, but is very cheap and removes the annoyance of seeing a clear optimization opportunity in the generated Core, so I'm going to pursue it. |
/benchmark plutus-benchmark:validation |
Comparing benchmark results of 'plutus-benchmark:validation' on 'dc9275462' (base) and '6a1211d67' (PR)
|
-1.69% on average. That's a bit better. |
/benchmark plutus-benchmark:validation |
Comparing benchmark results of 'plutus-benchmark:validation' on 'dc9275462' (base) and 'd6fdc931a' (PR)
|
Actually, thinking about it... The idea is trivial, but the implementation is some pretty annoying boilerplate, plus there are three ways to implement what's in here, all subtly different, all for 1.7% speedup that we'll get anyway if we just make |
Yeah, I'm happy to drop this. |
Don't look here yet.