You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
TEST_CASE_CLASS works with version 2.4.7, not with v2.4.8. It is broken by commit 95a7853.
Steps to reproduce
TEST_CASE_CLASS is not documented nor tested by the CI. However if I take this example proposed in the description of the feature, and simplify it :
#include "doctest/doctest.h"
class my_type {
int data = 5;
TEST_CASE_CLASS("all_to_all_v 2") {
my_type local;
CHECK(local.data == 2);
}
};
This does not compile. GCC error message:
doctest.h:1980:64: error: 'DOCTEST_ANON_VAR_4' was not declared in this scope; did you mean 'DOCTEST_ANON_VAR_0'?
1980 | global_prefix DOCTEST_GLOBAL_NO_WARNINGS(DOCTEST_ANONYMOUS(DOCTEST_ANON_VAR_),
Extra information
Note that a (better?) alternative to TEST_CASE_CLASS is mentioned here. Maybe we should try to implement the more flexible feature rather than fixing this one.
On a personal note, I was just trying to check if TEST_CASE_CLASS could solve my problem (a bug in MPI_TEST_CASE with several SUBCASE). But it will not (even when fixed). So I personally don't need the fix.
doctest version: v2.4.8
Operating System: Linux
Compiler+version: GCC 11
The text was updated successfully, but these errors were encountered:
Description
TEST_CASE_CLASS
works with version 2.4.7, not with v2.4.8. It is broken by commit 95a7853.Steps to reproduce
TEST_CASE_CLASS
is not documented nor tested by the CI. However if I take this example proposed in the description of the feature, and simplify it :This does not compile. GCC error message:
Extra information
Note that a (better?) alternative to
TEST_CASE_CLASS
is mentioned here. Maybe we should try to implement the more flexible feature rather than fixing this one.On a personal note, I was just trying to check if
TEST_CASE_CLASS
could solve my problem (a bug inMPI_TEST_CASE
with severalSUBCASE
). But it will not (even when fixed). So I personally don't need the fix.The text was updated successfully, but these errors were encountered: