Some discussion

https://news.ycombinator.com/item?id=47631118

Is this meant to go to... a _particular_ search?

Yes.

https://github.com/search?q=%22%E2%9A%A1+Quickly+spin+up+cop...

So, 11.3k results already.

If 0 is at the bottom of your range, not the top, put it next to 1 on the input row, not 9.

Thank you. Great suggestion. I've deployed the change.

Dupe

https://news.ycombinator.com/item?id=47555556

18 hours ago, 188 comments

I assume GP is talking about the bit in the article that goes

> RCT does this trick all the time, and even in its OpenRCT2 version, this syntax hasn’t been changed, since compilers won’t do this optimization for you.

That makes more sense, I second their sentiment, modern compilers will do this. I guess the trick is knowing to use numbers that have these options.

There was a recent article on HN about which compiler optimizations would occur and which wouldn't and it was surprising in two ways - first, it would make some that you might not expect, and it would not make others that you would - because in some obscure calling method, it wouldn't work. Fixing that path would usually get the expected optimization.