> I've also argued for degradation to bignums as the best default. It has sense for Python and Perl code but not for the code produced by something that would

> I've also argued for degradation to bignums as the best default. It has sense for Python and Perl code but not for the code produced by something that would be better C than the current C. If the performance is critical (as to have to effectively no slowdown compared to what the CPU can achieve), the CPU machine code instructions already do "the right thing" and it's the HL languages that abstract the carry or the saturation away to make the wrong plain "+". C with the CPU-specific extensions can "do the right thing." It's the "standard" "language lawyers" that are once again wrong.