assert is not a particularly appropriate model for Google Test's ASSERT_ macros. ASSERT_ macros are evaluated in Release builds, so the diagnostic assertWithSideEffect does not reasonably apply.
I don't know what the ideal model would be, but at least the model used for EXPECT_ macros would avoid the false-positive assertWithSideEffect findings.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Thanks! Sounds reasonable. I guess something that uses throw/exit would be a better idea. If you have time to look into this feel free to provide a github pull request.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
assert is not a particularly appropriate model for Google Test's ASSERT_ macros. ASSERT_ macros are evaluated in Release builds, so the diagnostic assertWithSideEffect does not reasonably apply.
I don't know what the ideal model would be, but at least the model used for EXPECT_ macros would avoid the false-positive assertWithSideEffect findings.
Thanks! Sounds reasonable. I guess something that uses throw/exit would be a better idea. If you have time to look into this feel free to provide a github pull request.