Hi @nlohmann and other mainteners,

First of all, I must say that I love your work on this librairy.
It feels really easy to use, and to read code using this library ! ❤️

I have created this issue to talk about the warnings that cppcheck found on this project.
I'm currently experimenting with both this library and cppcheck on some little side projects. A

Hello there! Cool framework project!!

It accepts translation to Portuguese-Brazil in documentations?

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

Description

I'm trying to use what the Qt landscape calls a "data driven testing". Here's my code:

TEST_CASE("converting a byte buffer to a float")
{
    float f;
    std::string buffer;

    DOCTEST_SUBCASE("0x41480000 (= 12.5)") { buffer = "\x00\x00\x48\x41"s; f = 12.5f; }
    DOCTEST_SUBCASE("0x3dcccccd (= 0.1)") 

GCC appears to evaluate transform function calls out of order, which I think it's allowed to do because function argument evaluation order is undefined. Hana should explicitly document the lack of ordering guarantees in transform.

We'd appreciate a PR to add CI tests for Android. Ideally, we are looking for a maintainer that also takes care of maintenance of those jobs and Android support in general.

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

It would be nice to read an overview of the technique used here. I tried reading through it but got a lost around n()

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