Compiler crimes


What if all software suddenly disappeared? What's the minimum you'd need to bootstrap a practical system? I decided to start with a one sector (512-byte) seed and find out how far I can get.

Go to series overview

Terminating the terminal case of Linux

I remember it like it was yesterday. It was a very calm and pleasant evening, when, all of a sudden, Amos, known also as fasterthanlime, published an article entitled "A terminal case of Linux". With a wonderfully punny title, he explains his adventure of getting colored terminal output out of a Linux process.

🤔 I sure do envy Amos's relationship with Cool Bear. I'd look into getting such a sidekick myself, but the dorm I'm about to move into doesn't allow keeping pets, and definitely not ones sentient enough to throw a party.

After a journey through the bowels of libc, the Land of Terrible Truths, and as is in Amos's style, many underlying details of the problem, we arrive at a program that does what we've set out to do. Well, almost. Read more

Compiling Rust is NP-hard

...though it's not the flagship borrow checking that's at fault. What I noticed, and would like to share with you today, is that the exhaustiveness checking performed by the Rust compiler on match patterns is a superset of the SAT problem. Read more

Twitter: @meithecatte • GitHub: @meithecatte • E-mail: catch-all on this domain