Oh, that’s right, I was using gcc.

Dude, after forcing -std=c++20, the compiler still can’t find a reference for std::ostream::operator<<(float)…

Do I have to link with some non-standard library? There doesn’t seem to have any numbers.a included with gcc.

Well, I can assure you that you have requirements.

You just don’t know what they are.

At least NaNs are different from each other and themselves.

SQL’s null would like a word here.

>> typeof(NaN)
<- "number"

It’s valid for C too, but it will be either a double or a float.

Yes, but if you shoot the airfryer, you won’t have an airfryer anymore.

for example, simply optimize it away

Yeah, that example makes it reasonable. But the optimizer can do ridiculous stuff when it proves the loop never terminates and also assume it terminates.

The most famous example of UB bullshit is when some compilers run code that is impossible to reach just because there’s an infinite loop on the file (not even in the same function).

Oh, JS’s this is fucked up to many levels above that theoretical issue the language also has.

And that line doesn’t help with the schizophrenia issue.