You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This concept was originally raised very early on #513. Since then #4178 enabled this information at the unit test level. We should be able to just extract this information from forc-test and display the byte code a gas used as an inlay hint next to the unit test.
Should provide a nice interactive way to golf byte size and gas costs for devs.
The text was updated successfully, but these errors were encountered:
This concept was originally raised very early on #513. Since then #4178 enabled this information at the unit test level. We should be able to just extract this information from
forc-test
and display the byte code a gas used as an inlay hint next to the unit test.Should provide a nice interactive way to golf byte size and gas costs for devs.
The text was updated successfully, but these errors were encountered: