After spending many happy years in Scala, not mutating anything but copying objects faster than rabbits breed I ventured into the world where each allocation is carefully examined and it is perfectly normal to reuse the same list for different purposes.
After spending many happy years in Scala, not mutating anything but copying objects faster than rabbits breed I ventured into the world where each allocation is carefully examined and it is perfectly normal to reuse the same list for different purposes.
Still, the types are as strong as ever, and one can feel (usually) rather safe. I’ll talk about things that surprised me or delighted me, as well as the ones that I still haven’t fully accepted (yet).
Should you dig the hype and default to Embassy when starting new microcontroller project? How it works and what does it bring to the table? Let's compare and measure the same IoT app written in sync and async Rust.
In this lightning talk, we take a look at ArcShift, a lock-free data structure for shared data that still needs to be mutated.
I applied PGO to many kinds of software, collected a lot of carefully hidden traps on my journey, and found multiple ways how to avoid them. In this talk, I want to share with you my experience.
In this talk, we'll explore reasoning with async Rust. We'll be introduced to its fundamental building blocks, such as `async`, `await`, `join` and `select`, and learn how to predict the behavior of code written with them.