28 Apr
2026
28 Apr
'26
8:41 p.m.
I endorse (u)int128.
Thank you Chris.
It should be a library, on its own, and be separate from Boost.Core.
Its purpose is to provide (u)int128_t for all platforms, and is seamless if the platform already has 128.
It is not a Multiprecision type. In fact, it much more closely resembles (u)int64_t (which is also kind of new in my world)
Clients of Boost.Multiprecision will hopefully not confuse this with a synthesized Multiprecision type. If confusion exists, it can easily be cleared up in ensuing chats or issues.
I've opened an issue to explain why this is separate, and should stay separate from Multiprecision. Matt