On Mon, Aug 7, 2023 at 9:48 AM Theo de Raadt <dera...@openbsd.org> wrote: > > enh <e...@google.com> wrote: > > > (fwiw, Android has someone working on adding this header to upstream > > LLVM right now, so hopefully it should come "for free" in llvm 18. > > what, if anything, to _do_ with it is another question though :-) ) > > Will stdckdint.h come into common usage before or after 32-bit time_t > wraps?
yeah, i'm not expecting to see much use any time soon. it feels like it would have been a good idea a few decades ago, but (especially with the awful names --- who missed out the 'h' that everyone types when they try to spell this?!) there's little to recommend this over just using the builtins directly. "the destination comes first" seems to be about it? i can't say i'm a huge fan of <stdbit.h> either, and given that it'll need to be done per-libc rather than just per-compiler i do wonder whether it will be another "annex k" [https://www.open-std.org/jtc1/sc22/wg14/www/docs/n1967.htm]. oh well, at least we finally got 0b literals and %b formatting, a mere 40 years late... (i'll grant them their first decade of "octal should be good enough for every PDP-11 programmer!" :-) ) > That's what I want to know. >
