Types of benefits you could expect:
Permissions: Try to remove every function modifier
Error handling: Prefer .transfer() over .call.value()
Bug finding: Tweak int literals to find off by one errors
Data types: Do you need uint256?
Visibility: Can this be private?
-
-
Show this thread
-
People talk a lot about formal verification for smart contracts. IMO, the more formality packed into a language, the harder it gets for less experienced devs. This is fine, but it caps how effective a tool can be. If you can write tests though you can use mutation testing.
Show this thread
End of conversation
New conversation -
-
-
OT: I did some initial experiments to write one for solidity. But I need to find a sponsor, do not have much of free time to do another one in the OSS.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
Most thorough code coverage metric
Easy to understand what changed
Recommends better practices
Mutation tester for Ruby