We are currently using C asserts as test assertions in our C API tests. That means our production builds don't include any assertions. A macro REQUIRE has been introduced, calling abort instead of assert; apart from printing some welcome annotations, like __FILE__, __LINE__ and the tested expression itself.
We are currently using C asserts as test assertions in our C API tests. That means our production builds don't include any assertions. A macro
REQUIREhas been introduced, calling abort instead of assert; apart from printing some welcome annotations, like__FILE__,__LINE__and the tested expression itself.