Unsafe-code-guidelines Alternatives

unsafe-code-guidelines reviews and mentions

• Zlib-rs is faster than C
  10 projects | news.ycombinator.com | 16 Mar 2025

  This is definitely true right now, but I don't think it will always be the case.

  Unsafe Rust is currently extremely underspecified and underdocumented, but it's designed to be far more specifiable than C. For example: aliasing rules. When and how you're allowed to alias references in unsafe code is not at all documented and under much active discussion; whereas in C pointer aliasing rules are well defined but also completely insane (casting pointers to a different type in order to reinterpret the bytes of an object is often UB even in completely innocuous cases).

  Once Rust's memory model is fully specified and written down, unsafe Rust is trying to go for something much simpler, more teachable, and with less footguns than C.

  Huge props to Ralf Jung and the opsem team who are working on answering these questions & creating a formal specification: https://github.com/rust-lang/unsafe-code-guidelines/issues

• Passing nothing is surprisingly difficult
  2 projects | news.ycombinator.com | 16 Jan 2024

  Useful context on the Rust side is this issue [1]. It sounds like some of the author's concerns are addressed already.

  [1]: https://github.com/rust-lang/unsafe-code-guidelines/issues/4...

• Blog Post: Non-Send Futures When?
  2 projects | /r/rust | 10 Dec 2023

  Is this captured by one of the known soundness conflicts? If not then should consider adding it to the list.

• Are crates like vcell and volatile cell still unsound?
  1 project | /r/rust | 5 Jun 2023
• Question: Are there things for Unsafe Rust learn from Zig?
  2 projects | /r/rust | 1 Jun 2023

  There are some competing proposals for different memory models. Stacked borrows is the current proposal, but there are more work in the approproate WG.

• Let's thank who have helped us in the Rust Community together!
  9 projects | /r/rust | 28 May 2023

  Thank you /u/RalfJung for bringing formal methods to Rust, both through models like Stacked Borrows, by developing miri, and by working on unsafe-code-guidelines which aims to specify exactly what is and isn't allowed in unsafe code (surprisingly, it's an open question as 2023!)

• Questions about ownership rule
  2 projects | /r/rust | 23 May 2023
• Noob Here: Why doesn't this work?
  1 project | /r/rust | 16 Apr 2023

  You could imagine some way to make this safe for example automatically convert &'short &'long mut T to &'short &'short T, but it's non-trivial to prove they are safe at all, not to mention ensuring this is correctly implemented in the compiler. If you're interested there's also a discussion on whether the opposite (& & T to & &mut T) is sound here.

• When Zig is safer and faster than (unsafe) Rust
  3 projects | /r/rust | 7 Mar 2023

  Agreed! MIRI is so good, it still feels like magic to me. It also comforts me that the Rust team takes improving unsafe semantics seriously, with the past Unsafe Code Guidelines WG and today's operational semantics team (t-opsem).

• Safety and Soundness in Rust
  5 projects | news.ycombinator.com | 5 Mar 2023

  I think there are some aspects of this rule that are still undecided. See for example:

  - https://github.com/rust-lang/unsafe-code-guidelines/issues/8...

  - https://github.com/rust-lang/miri/issues/2732

• A note from our sponsor - InfluxDB
  influxdata.com | 29 Apr 2025

  Collect, organize, and act on massive volumes of high-resolution data to power real-time intelligent systems. Learn more →