mitchgrout

Looking back at this, I think my answer to the question would be no. Ultimately the point of a namespaced world is to provide some logical organisation of test state,...

Unfortunately `__VA_OPT__` forces you to C20 / C++20, so that would likely be a no-go. One option would be to add a macro that introduces a unique name into scope...

Issue still exists on 2.4.11. As a note, you have your desired behaviour if your `REQUIRE` is replaced with `CHECK`. However, `REQUIRE` is good practice for things like asserting valid...

I guess there's a slight issue around terminology. The overarching `SCENARIO` / `TEST_CASE` is a 'test' in the language of doctest, so stating `"if a REQUIRE() fails - execution of...

I don't believe that's going to work, since `TEST_CASE` will expand to a `static` variable declaration that uses your `needToSkip` variable. When the global ctor's are run, your test case...

I would support `#include ` / `#include "doctest.h"` as the way to properly include the library, as `` personally feels redundant. It also leaves `#include ` as an obvious choice...