Hacker News Reader

TL;DR: a one liner source file tells the compiler to set main as a 4GB array; in the process the compiler might run out of memory.

View on HN

s/4GB/4GBx4 = 16GB/

To add to this, a "tl;dr" is only useful if written by people who actually read the whole article. That is, written by people who did not apply "tl;dr" themselves.

In this particular case, the article clearly says:

> The array will contain 4294967295 integers, each with the size of four bytes, taking up 17179869180 bytes in total.

Later, the article again stresses again that you have to multiply by four:

> having the size of 10000 integers, that is, 40000 bytes

It's really hard to imagine how somebody who actually did read the article could have missed that.

Its easy it was too long so they didn't read they skimmed.

Well, right. So we're back to the starting proposition: That you shouldn't write a TL;DR if you didn't read the article.

Anyhow, this was more of a short blog post than a full article. It was a 2 minute read (not exactly a novel). And the thought experiments at the end are interesting, and illuminate some important points about how the language operates. Definitely worth the read.

I think their interpretation of "tl; dr" is: "it was too long so I didn't read it, and here is what I think anyway".

Reply on news.ycombinator.com