I think we should patch test/CMakeLists.txt to always use -Wall -Werror on *nix and the corresponding MSVC flags. It is way too easy to overlook a warning in the CI output as #1797 has shown.

@nlohmann Thoughts?

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

Hey, could I get full documentation or post example? I want to recive Post's like
http:/example.com/login/?username=tester&password=myPassword
But I don't understand the only example which I've found in readme.md

Or mayby any idea how url would looks like for this:

CROW_ROUTE(app, "/add_json")
.methods("POST"_method)
([](const crow::request& req){
    auto x = crow::json::load(req

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.

See https://github.com/Neargye/magic_enum#readme.

If someone tries both Better Enums and magic_enum, and there is a reason to prefer Better Enums, please leave a comment here.

Otherwise, I think we should recommend magic_enum and move Better Enums toward deprecation.

cc @Neargye

Hello,
Do you know about Conan?
Conan is modern dependency manager for C++. And will be great if your library will be available via package manager for other developers.

Here you can find example, how you can create package for the library.

If you have any questions, j

I'm not sure if this is the right place to remark this, but the documentation webpage has many links to the underlying zmq functions, but all links to those appear to be broken.

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

This repository's README.md is way too long. The documentation specifics should be in a separate .md file, on the wiki, or both; and the main README.md should focus on the sections other than the Detailed Examples. In fact, Overview is also too long; I'd stick to a couple of examples, no more than that for the repo landing page.

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

We have user-definable variadic dimensions now, but we need to develop some case studies we can document to guide users on how to take advantage of that. We probably also want some macros to simplify including new dimensions and making sure traits and things are auto-generated when a new dimension is defined.

If anyone comes up with something cool, post it here or in a PR and I'll include it in