The current verification setup and harness could be improved in 2 ways:
make MorphoHarness expose getters that return the struct. For information this is done for metamorpho, for example here. This allows to then call the fields of the returned struct (for example here), instead of having a tuple
extract out, in a Util.sol file, the functions that do not depend on the state of the contract. For example wad, or maxFee, or simply add them in the spec when it makes sense. This is because then it makes importing files awkward, and naming weird (we don't want to write MorphoHarness.WAD())
The current verification setup and harness could be improved in 2 ways:
MorphoHarness
expose getters that return the struct. For information this is done for metamorpho, for example here. This allows to then call the fields of the returned struct (for example here), instead of having a tupleUtil.sol
file, the functions that do not depend on the state of the contract. For examplewad
, ormaxFee
, or simply add them in the spec when it makes sense. This is because then it makes importing files awkward, and naming weird (we don't want to writeMorphoHarness.WAD()
)