2 Aug
2026
2 Aug
'26
2:55 p.m.
This is interesting. It shows why a library solution will never be a full substitute for a built-in type. For a similar reason, it would be a bad idea for this library implementation to fall back to an alias on a built-in type on platforms where it is available, as then users would not be able to reliably depend on being able to derive from the type to make extensions.
Regards, &rzej;
The types in the library are never an alias to other types; they are always a struct of two 64-bit words. When available (and performant) the built-ins will be leveraged for implementation of operations e.g. division can become static_cast<builtin_u128>(lib_lhs) / static_cast<builtin_u128>(lib_rhs). Matt