Unsafe Rust code doesn’t turn off the borrow checker, it basically just allows you to play with pointers and call code that the compiler can’t (or can’t right now) statically assert is sound. IE if you roll your own Vtable the functions are safe to call, but the compiler can’t tell so you have to use unsafe
Ok this is funny. Like “look bro, we rewrote bun in Rust because it’s ✨Safe✨ and all that”, and they’re not even trying lmao
In all seriousness, part of that issue probably comes from the original code already ignoring the safety features of Zig, and whatever LLM they used to port it just doing the most half-assed thing and doing a literal translation of the code.
The future of software development, ladies and gentlemen
Edit: rust safety
Yes I know unsafe in rust doesn’t mean unsafe code, it just that the compiler trusts you to correctly use the interfaces and references since it won’t check them inside such blocks
And they’re initially doing it without Rust’s
memory safetyborrow checker iirc, so a big part of the benefit isn’t thereUnsafe Rust code doesn’t turn off the borrow checker, it basically just allows you to play with pointers and call code that the compiler can’t (or can’t right now) statically assert is sound. IE if you roll your own Vtable the functions are safe to call, but the compiler can’t tell so you have to use unsafe
Ok this is funny. Like “look bro, we rewrote bun in Rust because it’s ✨Safe✨ and all that”, and they’re not even trying lmao
In all seriousness, part of that issue probably comes from the original code already ignoring the safety features of Zig, and whatever LLM they used to port it just doing the most half-assed thing and doing a literal translation of the code.
The future of software development, ladies and gentlemen
Edit: rust safety
Yes I know unsafe in rust doesn’t mean unsafe code, it just that the compiler trusts you to correctly use the interfaces and references since it won’t check them inside such blocks