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
miniblog.
Related Posts
12
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.)
15
I see that *up has become an increasingly common name for toolchain installers: rustup, ghcup, even juliaup.
I think Rust was the first to use this terminology? I'm curious how similar the different *up tools are.
2
I would have thought that invoking a C compiler would be a solved problem. Looking at Rust's cc crate there's a remarkable long tail of corner cases to fix.
Exotic CPUs, microarchitectures, compiler differences, operating system differences, etc.