Unreal Engine is not a library.

in case it's a genuine question, it's a template for the signature of the callable function

en.cppreference.com/w/cpp/utilit...

What other parts of the STL is the + operator used to append to the path while also adding a filesystem separator?

For future reference, in c++ use std::function instead of raw function pointers, and using instead of typedefs.

using CharacterLogicFunction = std::function<Tile(Character&)>;

In c++'s std::filesystem::path, the / operator is used by std::filesystem library to append to the path with the separator. The + operator is used to append to the path without the separator.

Don't use intuition, read the docs.

Disable the full line AI assisted code completion. If you're using Clion the setting is here:

Editor > General > Inline Completion > Enable local Full line completion suggestions

fyi `get_money` is the I/O manipulator while the other one, `money_get` is a facet.
In layman's terms, first one you can string together with other IO operations on streams, the other one is the parser alone.

I don't think lack of highlighter support in VSC is valid ground for any critique.

just watch some cppcon recordings on YouTube, you'll be pleasantly surprised on how modern the standard is

There's nothing vague about lifetimes. But you mentioning volatile makes me think you experienced something called execution reordering, read calls reordered before the actual write even happened.

Unfortunately that's just a bad design.

I doubt that's what happened. Compilers can't just "optimize away" the lifetime of your data.

Something must have been designed poorly, which is maybe difficult to hear but I'm sure that's the case.

Maybe it's funny because of the inconsistent naming?
Also the joke is copied twice, maybe a metaphor on how everything is unoriginal?

Is there anything specific that you experienced lately, that made you feel that "undefined behaviour" is everywhere?

Yes, that's because the compiler couldn't generate it. Most likely because some member of the class has an explicitly deleted copy assign operator.

And that's usually for a good reason.

I've heard about recursive mutex being better performance-wise, but from my own experience the speed is comparable, both on Linux and Windows.

I couldn't find any more articles about it though. At this point it feels like a here-say.

If they gave you the test, I assume you had C++ listed in your skillset? If not, that's just a bad job advertisement.

Keeping backward compatibility is important. You don't want to rewrite huge codebases just to compile with the newer compiler... It's important for the economy.
Imagine if operating systems didn't care for compatibility... Your software would be outdated and broken before you could even release it.

Do you mean the syntax or the standard library?

If you mean the standard, C++ is a general purpose programming language, certain aspects of the standard library might not be to your liking, but they're designed with GENERAL PURPOSE in mind.

What is it exactly that was bothering you?