The whole article is (voluntarily) an oversimplification of how things happen. It's mainly intended to create a mapping "C world" <-> "Rust world", and from th

The whole article is (voluntarily) an oversimplification of how things happen. It's mainly intended to create a mapping "C world" <-> "Rust world", and from there you can go into the multiple rabbit holes that are compiler designs. In the past, I've written some toy programming languages, targeting Assembly (nasm). The toolchain was mycompiler + nasm + ld. Very much like a straightforward cc+as+ld (which of course is more complex than this in 2022). Now, I'm writing a more serious programming language, targeting Rust. And I wanted to know more about the toolchain and rustc. I've been writing Rust code for a few months now, and I never stopped before to think about "what is a crate" or "how does it relates to C/C++ toolchains". As a friend of mine said: > Rust is easy, write shitty code and let the compiler tell you how to fix it.