> For maximum efficiency you'd avoid addc like hell, because it blocks internal precomputation, and use guarantees like he did, avoiding overflow better. Whether that is the case depends on the CPU. I hit memory…
For maximum efficiency, you should work in binary instead of base 10. Handling carries becomes more straightforward with the right primitives, for example __builtin_addc with GCC:…
Not sure if it has been mentioned yet, but I think the main reason why this title failed is the title. Most people probably never heard of "yerba mate", so to them, the title sounds like some kind of weird mating…
> For maximum efficiency you'd avoid addc like hell, because it blocks internal precomputation, and use guarantees like he did, avoiding overflow better. Whether that is the case depends on the CPU. I hit memory…
For maximum efficiency, you should work in binary instead of base 10. Handling carries becomes more straightforward with the right primitives, for example __builtin_addc with GCC:…
Not sure if it has been mentioned yet, but I think the main reason why this title failed is the title. Most people probably never heard of "yerba mate", so to them, the title sounds like some kind of weird mating…