This would’ve been a chance for a TODO.

I wouldn’t mind the open source part, at least we can see why it breaks.

Not even that. Switching code flows means potential void of state integrity. Error handling should either terminate discarded states or not interfere at all.

By the way, imagine smart pointers with goto jumps.

That is until you’re doing something more complex, then goto becomes no-go.

This is the spirit

Agreed, but in terms of efficiency wouldn’t it make more sense to put the sign bit right before the mantissa in order to keep the memory layout more consistent with powers of two?

I think it’s not meant to be more traditional, the icon positions seem random and only the square they’re located is important.

.mng to the rescue!

That’s not even DOS I think. As far as I know Win 95 came up with this monstrosity in an attempt to circumvent the 8.3 character limitations present in older versions of DOS.

I think that may be possible for every filesystem supporting UTF-8 encoding.

Well… and what would be the meta templating equivalent to this statement?

What!? constexpr is one of the best additions to C++ ever since. And I do like auto even though I get why some folks can’t stand it.

Did you know that there is a debugger in Jetbrains CLion (and I think VS as well) that allows you to step through your CMake scripts? As ridiculous as this may seem, actually it is really useful.