Thread

1. lexicality · 1790501356 · focus · HN ↗

   I feel like the article glosses over the fact that (to my mind) `int_fast32_t` and `int_least32_t` are a much better solution than "int is a random size good luck"

   If you code exclusively using those types (and the `*ptr_t` ones) then you precisely express to both the compiler and the next person reading it what is supposed to be in those variables.

   1. mmoll · 1790501817 · focus · HN ↗

      I came here to say exactly that. There’s int_leastN_t for storage and int_fastN_t for computation. Stdint.h really gets a bad rap here.

      1. lexicality · 1790501948 · focus · HN ↗

         fwiw depending on use cases you might actually want to be using the fast variants for storage too, for example on arm64 you'll get aligned memory loads

Unofficial Hacker News client; not affiliated with Y Combinator.