Skip to content
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

feature --gas-report-diff #8774

Closed
fico23 opened this issue Mar 20, 2024 · 1 comment
Closed

feature --gas-report-diff #8774

fico23 opened this issue Mar 20, 2024 · 1 comment
Labels
T-needs-triage Type: this issue needs to be labelled

Comments

@fico23
Copy link

fico23 commented Mar 20, 2024

forge snapshot --diff offers valuable insights into overall gas consumption changes, yet it can sometimes lack granularity due to multiple function calls within tests. Introducing a forge test --gas-report-diff command could provide a more detailed comparison of gas usage at the function(and deployment) level. This feature would complement the existing forge test --gas-report, enabling developers to pinpoint specific changes in gas consumption with greater precision. Such an enhancement would be incredibly useful for optimizing contract efficiency.

@onbjerg onbjerg transferred this issue from foundry-rs/book Aug 29, 2024
@zerosnacks zerosnacks added the T-needs-triage Type: this issue needs to be labelled label Sep 12, 2024
@zerosnacks
Copy link
Member

Hi @fico23 thanks for your suggestion

I think what you are looking for will be addressed in #8755

Feel free to join the conversation in #2065

If this is not the case feel free to re-open the ticket

@zerosnacks zerosnacks closed this as not planned Won't fix, can't repro, duplicate, stale Sep 12, 2024
@github-project-automation github-project-automation bot moved this from Todo to Done in Foundry Book Sep 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
T-needs-triage Type: this issue needs to be labelled
Projects
No open projects
Status: Done
Development

No branches or pull requests

2 participants