We can allow non-exiting gtest assertions to be called in constructors and destructors and simply throw to exit the functions ourselves.
If we want to keep track of things the user should do for migration we can do so with a constexpr check of __FUNCSIG__ and __PRETTY_FUNCTION__ Should be done under new issue
We can allow non-exiting gtest assertions to be called in constructors and destructors and simply throw to exit the functions ourselves.
If we want to keep track of things the user should do for migration we can do so with a constexpr check ofShould be done under new issue__FUNCSIG__and__PRETTY_FUNCTION__