HN Hall of Fame Weekly email

What every compiler writer should know about programmers [pdf]

www.complang.tuwien.ac.at Research & data Research papers Computer science Candidate
Screenshot of www.complang.tuwien.ac.at captured 2026-07-20
Page preview · captured 2026-07-20

Resurfaced independently across 3 calendar years, with breakout response in 2 of them.

submissions
4
submitters
3
observed span
2016–2019
peak thread · 106 comments
122 pts
latest 20+ return · 2019-04-14
88 pts

Submission timeline

2007–2026

One slot for every year since HN launched. Height is that year's peak points; orange marks a 100+ point or 50+ comment breakout. Select a bar to open its strongest thread.

First comments on top threads

HN comment order

One of the things this person misses is a lot of these are undefined with the explicit goal to let compiler authors take advantage of them. So his real argument is with the C committee for not defining these things the way he wants them. His claim that the behavior of what should happen is obvious is pretty strange (IE "it should do exactly whatever the compiler is trying to prove it doesn't") It's essentially a complaint that compiler authors…

The author seems to be saying, in section 4, that compilers should just stop doing some optimizations (such as converting int to size_t where appropriate) and should expect programmers to do those optimizations instead, in order to reduce undefined behavior. The problem with this argument is that it doesn't match economic reality. Compiler authors wouldn't disagree that it would be nice to not have to do these optimizations! (Chris Lattner has said as much to me, for example.) Unfortunately, there…

The first top-level comment from each of the four biggest threads, in HN’s own order. Excerpts are shortened; open a comment for full context.

Breakout years
2

100+ points or 50+ comments

Total points
214

reference only — not used in Hall rules or ranking

Total comments
168

reference only — not used in Hall rules or ranking

Every submission