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
{{ message }}
This repository has been archived by the owner on Aug 20, 2021. It is now read-only.
When auditing a contract it is useful to have a full overview of all methods that can be used to mutate state. The method list overview in the report currently mixes accessors and mutators, making it a little harder than it needs to be to get this information.
It would be nice if there would be some split or visual differentiation between methods that mutate and those that don't. This information could be extracted from the specs, as methods that mutate have their <static> cell set to false.
The text was updated successfully, but these errors were encountered:
When auditing a contract it is useful to have a full overview of all methods that can be used to mutate state. The method list overview in the report currently mixes accessors and mutators, making it a little harder than it needs to be to get this information.
It would be nice if there would be some split or visual differentiation between methods that mutate and those that don't. This information could be extracted from the specs, as methods that mutate have their
<static>
cell set to false.The text was updated successfully, but these errors were encountered: