Add option to report view & pure method gas usage
See original GitHub issueWe should be able to use estimateGas
for these.
It impairs test speeds but this data is important for libraries.
(See prb-math 70)
Issue Analytics
- State:
- Created 2 years ago
- Reactions:12
- Comments:6 (2 by maintainers)
Top Results From Across the Web
ASPEN Tutorial | Chemical Engineering and Materials Science
To add these property sets to a stream report, Setup -> Report Options -> Stream Report Tab -> Click the 'Property Sets' button...
Read more >Revisions and Confidentiality Determinations for Data ...
More recently, the EPA finalized edits to the petroleum and natural gas systems source category to address potential gaps in coverage, improve ...
Read more >Answers to Frequently Asked Questions - NIST Pages
The REFPROP “database” is actually a program and does not contain any experimental information, aside from the critical and triple points of the...
Read more >FAQ : PURE.APP
HOW DO I HIDE SOMEONE'S AD FROM MY FEED? Sometimes, we all just wanna unsee things. By clicking on the menu, you will...
Read more >Login - DTE Energy
Log in to your DTE Energy online account to pay your bill, manage payment methods and enroll in energy-saving programs.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Ah, that’s way more than I expected. If it really slows things down that much then yeah, it might make sense to keep if off by default.
BTW, let me know if you need help benchmarking it on some real-life projects. We have a nice setup in Solidity where we run a bunch of them (13+ mid to large projects, including OpenZeppelin, Uniswap v3, Gnosis, etc) in CI to test the compiler. As a part of this we can see a breakdown of how long each one took to run the whole test suite: https://app.circleci.com/pipelines/github/ethereum/solidity/22003/workflows/92d7ef3e-f94a-448c-9db1-16cc18d19e9a (all the
t_native_test_ext_...
jobs are such projects). The time includes compilation, dependency installation, etc. but on the upside it would also show how relevant the slowdown is compared to other factors.This would be very useful for SolidState.