They’re great for a NAS, where the priority is high capacity and low cost, over high performance and high cost of SSDs for comparable capacity.

That doesn’t work if either one is NaN

What was even the point of introducing the legacy assertion module? We’ve known for decades that using == is not a good idea. They should have just killed it while the thing is experimental, instead of letting it get into the stable module.

The extra effort required to explicitly import the strict assertion module, instead of getting it by default, is going to lead to lazy developers inadvertently getting the legacy mode, that shouldn’t exist for a new assertion module.

My indentation is secretly the actual program written in the whitespace programming language.