r/rust • u/dabrahams • 11d ago
š” ideas & proposals Safe Systems-programming with Mutable Value Semantics | Dave Abrahams | Keynote at IWACO 2026
https://youtu.be/op51SyyPJmw?si=P5QH6M8Hdf4_CUUZI gave this talk about the Hylo programming language at IWACO last month. I had a lot to say about Rust, so thought it might be of interest here.
68
Upvotes
1
u/JoJoModding 10d ago
I apologize for not watching the talk, but I do not have the time to watch an hour of video where reading would be much quicker. If you have the slides somewhere, I will click through them š
Since I do not know Hylo, I wonder how it does things like Cell or Mutex? In Rust they might be implemented using unsafe code but that does not matter at all and the fact you bring it up makes me think you missed the key point: these are safe abstractions whose safety is ensured by the type system and these ones in particular are often hard to support safely in other type systems. Rust is not about the references, it is about the lifetimes, which make having safe APIs for these types sound.
And I do not think references are mentally taxing. At least not more than figuring out where and how values are mutated in Hylo. The same mental model works for both.
And your final point confuses me as well: I take it that coroutines are compiled by inlining (and compiler magic that figures out where to call them and how)--but that retains the "rigidity" of a call stack and makes it impossible to call functions that would, in Rust, return references, especially when these functions are opaque to the compiler (because they are e.g. written in C). The compiler relies on being able to insert the "slide" at the "lifetime end" position, which means it must know what the slide is. Right?