I believe a restriction for `constexpr`/`consteval` is that you can do memory allocations but they must all be freed at the end of the evaluation. Arbitrary precision means arbitrary memory usage means allocation that's the runtime's responsibility. Maybe there's a trick that gets around that (define a type at compile time that's just big enough for this specific number and return that?), but I don't see it as possible without something weird.