Describe the bug
When TEMPLATE_LIST_TEST_CASE and TEMPLATE_LIST_TEST_CASE_METHOD were added, the corresponding versions with the CATCH_ prefix were missed.

Expected behavior
CATCH_TEMPLATE_LIST_TEST_CASE and CATCH_TEMPLATE_LIST_TEST_CASE_METHOD should be available.

Additional context

The commit that added TEMPLATE_LIST_TEST_CASE and `TEMPLATE_LIST_TEST_CASE_MET

I couldn't find this in the documentation or the FAQ: Is it possible to obtain the current test case's name from within that testcase's code? I mean, it should be, but how do we do it? That should be either in the FAQ or in some other relevant documentation file, IMHO.

Add API nameof::cstring to https://github.com/Neargye/nameof/blob/master/doc/reference.md

The Guidelines Support Library is sort-of documented in the C++ Core Guidelines, so one could argue that GSL implementations such as gsl-lite only need to document their configuration switches.

However, gsl-lite offers a variety of additional features which are currently undocumented (e.g. the gsl_HAVE_* family of macro

When using LAY_BOTTOM or LAY_RIGHT anchors for an item's behavior, it doens't subtract the "left" margin, leaving you with an invalid offset: (yellow rectangles are the margins)

Changing the code to the following fixes the problem:

case LAY_RIGHT:
    child_rect[dim] += 

Reading gb_math.h source sometimes is really confusing.
Usual math notation for matrix is Aij where i is row and j is column:

A00 A01 A02 A03
A10 A11 A12 A13
A20 A21 A22 A23
A30 A31 A32 A33

Note that this notation is memory-layout free, this is just how matrices are written down on paper in generic science/engineering notation.

Considering this:

typedef union gbMat4 {
	st

I started using Catch recently, and then saw this library mentioned somewhere. In the Readme you describe it as based on the ideas of Catch. It would be useful to see some kind of comparison with Catch, such as "it is like Catch (as of version 1.1) but adds XXX and YYY. On the downside it doesn't have ZZZ of Catch, and Catch compiles more quickly".

Unless it was a personal exercise in writing a

If you declare a string constant in the global space you might see clang-tidy showing the warning that "Initialization of X with static storage duration may throw an exception that cannot be caught".
Actually initialization of the constant literal string never throws an exception.

Example:

const char* path = "file:///path/to/file.ext";

To fix it the following constructors shou

See PR #11

• Acknowledgment: mention configurable visitor
• Add section on configuring variant types and visitor arguments (mentioned in In a nutshell)
• Update table

Having spent several hours yesterday pairing with a new user, we copied a lot of examples from our docs, and in every case, we had to paste in our namespace ApprovalTests:: - it got very old, very quickly - and I ended up agreeing with this:

https://twitter.com/lefticus/status/1207890691948339200

Please, I implore you, in the name of all that is good, do NOT use using namespace in

Make the output, especially as generated by the macros TEST_CHECK(), TEST_MSG() and TEST_DUMP(), automatically adapt to the current terminal size, so that it looks good in a reasonably small terminal window but can use effectively more space if the terminal window is big.

This should involve:

0. Explore what API is available for the purpose on the platform of your choice.
1. A pre-pro

(issue corresponding to review suggestion here)

CMAKE_CXX_FLAGS is used to configure compiler warnings in cmake as part of the testing procedure, (following the this advice). I am not aware of a warning API in cmake and I know of no option that does not involve passing e