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?

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.