Inspecting rustc LLVM optimization remarks using cargo-remark

TLDR: I think that the primary benefit of async/await is that it lets us concisely express complex concurrency; any (potential) performance improvements are just a second-order effect. We should thus judge async primarily based on how it simplifies our code, not how (or if) it makes the code faster.

I’m still recovering from the most hectic semester of my life1, so I wasn’t yet able to push out the several blog posts that I have in the pipeline. So this is just a short post in which I wanted to share a bunch of Rust exercises that I created during the first run of a Rust university course that I was teaching at my university this semester....

I haven’t been blogging for the past ~eight months, because I was quite busy finishing my PhD thesis. I have finally submitted it by the end of August, and as of today, I have also succesfully defended it, which marks the end of my six (!) years1 long PhD study in the area of High-Performance Computing and Computer Science. My PhD study...

Rust compilation times is an ongoing topic that generates many discussions online1. Most people don’t really care about what exactly takes time when compiling Rust program; they just want it to be faster in general. But sometimes, you can see people pointing fingers at specific culprits, like LLVM or the borrow checker. In this post, I’ll try to...

TL;DR: I created a Cargo subcommand called cargo-wizard that simplifies the configuration of Cargo projects for maximum runtime performance, fastest compilation time or minimal binary size.