Because even with the smallest base of 2, there's no way we're realistically going to overflow uintmax_t with the answer, regardless if it's a 32-bit or 64-bit system. That number of bits is only one eighth of the total number of bytes we could ever hope to address with such a system, and represents a truly astronomical number!
In the interests of efficiency, we will return the result as a pair of native types instead of using arby::Nat for this.
Because even with the smallest base of 2, there's no way we're realistically going to overflow
uintmax_t
with the answer, regardless if it's a 32-bit or 64-bit system. That number of bits is only one eighth of the total number of bytes we could ever hope to address with such a system, and represents a truly astronomical number!In the interests of efficiency, we will return the result as a pair of native types instead of using
arby::Nat
for this.