Is this something we actually want to do? I'm a fan of <types.h> as an "all the random types and macro crap you may need" include... because do you actually want to memorize whether size_t is in stdint.h or stddef.h? And always include both of those because any non-trivial amount of function prototypes probably needs both a fixed-length integer and size_t/uintptr_t somewhere? I think there's something to be said for standardizing on a single fire-and-forget header that covers all this basic infrastructure crap for us.

View Change

To view, visit change 31892. To unsubscribe, or for help writing mail filters, visit settings.