Cancelling async Rust ꞏ sunshowers
Correctness in the face of cancellations: a written version of my talk at RustConf 2025.| Cancelling async Rust
Correctness in the face of cancellations: a written version of my talk at RustConf 2025.| Cancelling async Rust
| Zed Industries - Blog
A few years back I proposed view types as an extension to Rust’s type system to let us address the problem of (false) inter-procedural borrow conflicts. The basic idea is to introduce a “view type” {f1, f2} Type1, meaning “an instance of Type where you can only access the fields f1 or f2”. The main purpose is to let you write function signatures like & {f1, f2} self or &mut {f1, f2} self that define what fields a given type might access.| All Posts on baby steps
Or: The Most Expensive Linked List I’ve Ever Written| Chad Austin
This post lays out a 4-part roadmap for the borrow checker that I call “the borrow checker within”. These changes are meant to help Rust become a better version of itself, enabling patterns of code which feel like they fit within Rust’s spirit, but run afoul of the letter of its law. I feel fairly comfortable with the design for each of these items, though work remains to scope out the details. My belief is that a-mir-formality will make a perfect place to do that work.| smallcultfollowing.com
The article is also available in Chinese.| loglog.games
Lock-freedom without garbage collection| aturon.github.io
A hash map implemented with quadratic probing and SIMD lookup.| doc.rust-lang.org
Manually manage memory through raw pointers.| doc.rust-lang.org
A contiguous growable array type, written as `Vec`, short for ‘vector’.| doc.rust-lang.org
Imagine you wrote a program for a pleasingly parallel problem, where each thread does its own independent piece of work, and the threads don’t need to coordi...| pkolaczk.github.io
