Rust’s ownership rules
1. Every value in Rust must have a single owner
2. A value can have any number of immutable references
3. You can only create a single mutable reference to a value
4. If there’s a mutable reference to a value, you cannot have an immutable reference to it
Joined May 2022
- It’s exciting how much of modern JavaScript tooling is adopting Rust! There’s swc, turbopack, turborepo rewrite (nice work @vercel friends), the new parcel CSS compiler and now the new Tailwind compiler. It’s great to see.Whipped up a tiny abstraction to make it easier to run the Tailwind test suite against both our stable engine and the new Rust stuff... Couldn't resist the name 🏒🥅
- Getting the finishing touches in on the Building an API server module. We’re going to build an API that runs on @flydotio and persists answers to Postgres for quiz questions for the course. Coming next week!
- In Rust, it is possible to force-ably allocate values on the heap using the Box type, here is an example of an i32 value allocated on the heap. age is now a pointer to a heap allocated i32.
- Rust lets you iterate through something iterable using an Iterator. Here's an example of filtering an array for even numbers. We create an Iterator from our array using into_iter in this case, a version of iter that moves ownership of each value into our closure.


