Every story and comment from the Hacker News API, in a layout borrowed from 2001.
A comment on The Value of Undefined Behavior. Parent comment
Magic behavior of "int" (but not "unsigned int") --> just use a type that's the correct size and better conveys your intention, like "size_t".
(And that one doesn't make your code "many times faster", in the example given it saves a single instruction.)
Type-based assumptions about aliasing (with a special case for char*) --> be explicit about your intention with the "restrict" keyword.
There are no comments on this comment yet.
Magic behavior of "int" (but not "unsigned int") --> just use a type that's the correct size and better conveys your intention, like "size_t".
(And that one doesn't make your code "many times faster", in the example given it saves a single instruction.)
Type-based assumptions about aliasing (with a special case for char*) --> be explicit about your intention with the "restrict" keyword.