An unsoundness in Rust using only safe code!
Rust provides a bunch of guarantees so it's always interesting to see the rare ways it can be broken. I think this is the first unsoundness since the thread spawn issue after 1.0?
https://internals.rust-lang.org/t/unsoundness-in-pin/11311
Related Posts
It's interesting to see the "why not Rust?" discussions around the TypeScript news that they're using Go. It shows that Rust has reached a level of maturity that it's a default for some users.
Go does seem to be in a sweet spot for AOT languages with GC though.
It's really satisfying to use a profiler for the first time on a project. I always find a big performance win with only a small code change.
It's never the code that I expected to be slow, however!
Claude asked me a question today: was I looking for an Emacs plugin (because I was talking about elisp) or a Rust program (because I have configured Rust preferences)?
I'm really impressed, it's rare to see LLMs ask follow-up questions.
(I wanted Emacs in this case.)