Yes, for the most part intmax_t (and similar guarantees) is considered a mistake. In C++, the next mistake is going to be the hardware_{constructive,destructiv

Yes, for the most part intmax_t (and similar guarantees) is considered a mistake. In C++, the next mistake is going to be the hardware_{constructive,destructive}_interference_size constants that have serious ABI implications. I think that current GCC position is that they are not part of the ABI and they are subject to change (but also controllable from the command line).