Types that pin data to a location in memory.| doc.rust-lang.org
Or: The Most Expensive Linked List I’ve Ever Written| Chad Austin
In July, boats presented a compelling vision in their post pinned places. With the Overwrite trait that I introduced in my previous post, however, I think we can get somewhere even more compelling, albeit at the cost of a tricky transition. As I will argue in this post, the Overwrite trait effectively becomes a better version of the existing Unpin trait, one that effects not only pinned references but also regular &mut references. Through this it’s able to make Pin fit much more seamlessly ...| smallcultfollowing.com
Contents| safecpp.org
The Pin type (and the concept of pinning in general) is a foundational building block on which| without.boats
Ergonomic Self-Referential Types for Rust| blog.yoshuawuyts.com
Parts of the Rust language may look familiar to C programmers, but the two languages differ in [...]| LWN.net
In my last post I introduced an Emacs Lisp VM I was writing in Rust. My stated goal at the time was to complete a garbage collector. I think Rust has some really interesting properties that will make building garbage collectors easier and safer. Many of the techniques used in my GC are not original and have been developed by other Rustaceans in previous projects. Updated: 2022-09-06 Why use garbage collection?| coredumped.dev
Types that pin data to a location in memory.| doc.rust-lang.org
I’ve been told I need to write this idea down – I figure this one’s a good enough excuse to start one of them programming blogs.| mcyoung.xyz