In OpenZeppelin, we're considering dropping some of our asserts and changing them to require (see here for some relevant discussion), changing the semantics of assert to 'shouldn't ever fail unless the code is buggy'. Because of that, solidity-coverage will report a line with partial coverage on each assert.
Could the requirement of assert failure being covered be dropped, or an option added to disable it (maybe with a huge error flag if the assertion ended up failing)? We'd hate to have our coverage figure drop because of a semantics difference.
Thank you for your time and awesome work!
In OpenZeppelin, we're considering dropping some of our
asserts and changing them torequire(see here for some relevant discussion), changing the semantics ofassertto 'shouldn't ever fail unless the code is buggy'. Because of that,solidity-coveragewill report a line with partial coverage on eachassert.Could the requirement of
assertfailure being covered be dropped, or an option added to disable it (maybe with a huge error flag if the assertion ended up failing)? We'd hate to have our coverage figure drop because of a semantics difference.Thank you for your time and awesome work!