What to do with `debug_assert!`s inside this crate?
fitzgen opened this issue · 0 comments
fitzgen commented
thought: should we be including this? fuzzing is usually run with debug assertions on so the debug_assert doesn't get us much. I am comfortable with more thoroughly documenting the safety situation instead
Originally posted by @Manishearth in #151 (comment)
Another option is adding a test_assert! macro that is guarded on cfg(test), so it only runs for this crate's tests.