1. Add uint8_t, uint16_t and uint32_t to the table. May not exist, but it is ridiculous if those do not work.
Thanks, I updated the paper to explain that
charN_t is always defined to have a uint_leastN_t underlying representation, on all platforms, so that's what the wording uses.
On platforms where they are defined (thankfully, the vast majority of them) uintN_t are aliases of uint_leastN_t
So if they exist, they work.
2. Rephrase nuking. Try not to use war terms for programming language design.
Rest lgtm.