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
It would be useful to get a report of the distribution of function calls at the end of a successful invariant test run.
Users currently have to resort to manually instrumenting the function calls by adding storage vars, which clutters the handler contracts with logic that is unrelated to the actual business logic of the protocol. See, for example, the numCalls mapping defined in Lucas' invariant-examples repo, and also his invariant_call_summary function.
This is something that should be done by Forge, which is in charge of orchestrating the invariant tests anyway.
The text was updated successfully, but these errors were encountered:
Component
Forge
Describe the feature you would like
It would be useful to get a report of the distribution of function calls at the end of a successful invariant test run.
Users currently have to resort to manually instrumenting the function calls by adding storage vars, which clutters the handler contracts with logic that is unrelated to the actual business logic of the protocol. See, for example, the
numCalls
mapping defined in Lucas'invariant-examples
repo, and also hisinvariant_call_summary
function.This is something that should be done by Forge, which is in charge of orchestrating the invariant tests anyway.
The text was updated successfully, but these errors were encountered: