Likely they're confusing it with bitwise OR, since in C, a | b == c parses as a | (b == c), causing widespread pain.

I want to believe that this is satire

JavaScript has a whole definition of equality for this particular case called SameValueZero: https://tc39.es/ecma262/multipage/abstract-operations.html#s... Everything is compared bitwise equal (so to speak), except 0 == -0.

    > new Map().set(-0, -0).set(0, 0).set(NaN, NaN)
    Map { 0 → 0, NaN → NaN }

I don't really understand the reason for this instead of Object.is equality (aka SameValue), which would distinguish -0 and 0.

Super cool :)

Has all this analysis of the die shot ever led to the discovery of novel bugs in the 8086?

The parents you talk about just seem like assholes.

> Those advocates with low support needs are the ones that are actually making an attempt to give those high support needs a voice.

Having low-support-needs autism is neither necessary nor sufficient for being a good voice for others. In fact, it can be a very bad thing, if they imply that the problems they face are similar to problems faced by high-support-needs folks. The focus in the media on low-support-needs individuals gives people the wrong impression of the autism spectrum's individual experience and broader societal impact.

I think a better form of advocacy is the YouTube channel "Special Books by Special Kids," which doesn't make a point of the channel's author having a disability (no clue whether he does), but rather just introduces viewers to a broad variety of people.

Even syntactically, TS is not a superset of JS: https://anemato.de/blog/js-to-ts

So it's a "sodium chloride" thing. Oh I hit this case too, and even this article looks familiar, probably cause I googled an error message

It's the specter of a lawsuit that's the problem.

Love Scala! One of my favorite high school memories is putting Scala files into a DAW and hooking it up to an electric piano, so that my piano teacher and I could play around with different tunings.

I'd love if this could make it into Rust... but I'm wondering if it'd be a bit of a burden on the creators of alternative backends (e.g. Cranelift), since if they implemented it naively, they would be unsuitable for compiling cryptographic code using it.

> but I'm wondering if it'd be a bit of a burden on the creators of alternative backends (e.g. Cranelift)

Technically any new feature that requires backend support is an additional burden on backend devs. There's nothing special about constant-time builtins in this respect.

> since if they implemented it naively

Strictly speaking, whether an implementation is naive is independent of whether it is correct. An implementation that purports to be constant time while not actually being constant time is wrong, no matter how naive or sophisticated the implementation may be.

The solution is always another macro :)

#define ct_select __builtin_ct_select