Happy Birthday here too, my love 🩷🩷🩷

no, it's all good

Meow?

Does he want to terminate TLS himself or is he okay with a reverse proxy that forwards everything for all required domains to him on port 80?

Hmmm, you could make the acthal constructor private and move error-causing logic into a public static function that returns a std::expected<YourType, YourErrorCode>.

Hmm, maybe for cases in which the compiler can't tell that the end of the function will never be reached...

But for that a __builtin_unreachable(); return {}; would probably be better.

Well, as far as I can see, neither the Java langauge spec nor the JVM spec contain any information about the standard library.

If you cut the standard library part from the C++ spec, you are left with around 600-700 pages...

I'm using VSCodium with the CMake Tools and clangd extensions.
CMake Tools automates/integrates all CMake stuff pretty well and also generates a compile_commands.json, that clangd then picks up to provide pretty good and fast Intellisense (which I prefer over VSCode's default).

Yeah, compiler support is spotty sadly :(
My favorite parts of it are compile times if you got big headers (importing a module is cheap) and getting rid of accidentally including build-breaking macros.
And it simplifies stuff a lot, since you no longer need to think about which headers you need.

I honestly like them a lot, especially since it is really easy to wrap existing non-module projects into a module. So when I use a third party library, I often just write a quick module wrapper for it.
And from my experience they work fine together with traditional includes most of the time.

Only thing I kind of wish for is using Snaps & Snapcraft inside a Docker container without having to manually extract and install everything.