Viewing profile — 0xd34df00d

I was mostly curious about how wc handles spaces and whether ignoring non-ascii spaces brings me closer or farther from what wc does. So I focused on that, and this specific printa…

No worries, that's a natural reaction! > In practice it's unlikely that you find yourself in a situation where you can write code in a high-level language that runs considerably fa…

> For reference, I'm referring to the "oops I did it again" part. It's really hard to take that comment as "honours go to GHC authors". Was overly excited when I created the repo a…

This is a great point about handling printable vs non-printable characters that I originally missed when I read wc code. Thank you for pointing this out!

> So until you put in locale handling, alternate line endings, option handling, and error handling, I don't see that your post is at all convincing. That's precisely what the secon…

Me neither. But experience shows that these titles lead to more folks looking at the post, leading to more feedback, leading to better writing/experimenting/etc in the long run. Al…

wc was actually slower with LC_ALL=C as opposed to ru_RU.UTF-8 that my system normally runs with (about 10 s against 7.2 s). Which actually raises a good question of whether I shou…

Those are fairly trivial and well-known optimizations that I did (and I by no means am an expert in writing high-performant code), so all the honors go to GHC authors.

Sup, author here. > Does the Haskell version really do the same thing as the C version? It counts bytes, words and lines and, modulo intended Unicode space handling and unintended …