Skip to content

Allow exiting assertions in constructors and destructors #37

Description

@OlekRaymond

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions