Right now we give the following information (e.g.):

openage v0.4.0-69-g9412facd
opengl
MSVC 19.16.27032.1 [/DWIN32 /D_WINDOWS /W3 /GR /EHsc /MP]
Cython 0.29.14

For future debugging on the user side we could give more information:

• OpenGL version number
• nyan-lib version number
• libc
• sdl-version
• Qt-version
• maybe even opus-codec version

In addition:
jj quote:

The doc is great! Hoewever some areas are still missing.
C++11 intoduced raw string literals: https://en.cppreference.com/w/cpp/language/string_literal

It is useful in many different areas, like strings with quotes, multiline strings and for example windows paths without escaping backslashes:

const char win_path[] = R"(c:\some\unescaped\path)";

The same cppreference link als

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)") 

I am still learning how to use sol (release 3.2, default configuration), and just wrote this today by mistake:

lua.new_usertype<player_list>("player", 
    "name", &player::name,
    // ... more stuff
);

lua.new_usertype<player_list>("player_list",
    "get_self", &player_list::get_self,
    // ... more stuff
);

Notice how I incorrectly specified the template parameter ``

For now the wiki page of OpenXRay is a mess!
I mean all necessary pages on all possible languages are trying to fit into main wiki page.
I haven't even found coding conventions from the first time!

That should be structured by the next design:

• Main page contains only links to language main wiki page.
• Language main page contains thematic sections like: Development, Modding, Using, Conti

As for Display the special operations generated by the compiler #224 discussion, the documentation will improve if we had a section describing the transformation of each featre and his limitations.

In particular for the special operation, to explain that only the operations that are really generated would appear in the transformation. This is due to the fact that the tool s based on the AST.

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.

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

the correct result of the example in Vc::iif should be [2,1,1,5] (if i understood it correctly)
and I am not sure whether the code example in Vc::simd_for_each is correct, therefore I did not make a PR.

void scale(std::vector<double> &data, double factor) {
  Vc::simd_for_each(data.begin(), data.end(), [&](auto v) {
     v *= factor;
  });
}

If one gets v by value, it chang

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