On Thursday, April 2, 2026, Marcin Jaczewski via Std-Proposals <std-proposals@lists.isocpp.org> wrote:
True, its has its benefits but atomic increment cost too and could
affect every core.
Looking at people who want 101% CPU and go out of their way to avoid
sharing cache lines between cores, seams like
this `big_int` will not be acceptable for them.
Or maybe have two ints? `big_int` and `big_int_shared`?
Don't you mean:
std::big_int
and:
std::atomic< std::big_int >
The latter could be specialised and optimised (instead of just allowing the compiler to use a mutex).