unsafe-code-guidelines

Forum for discussion about what unsafe code can and can't do (by rust-lang)

Unsafe-code-guidelines Alternatives

Similar projects and alternatives to unsafe-code-guidelines

NOTE: The number of mentions on this list indicates mentions on common posts plus user suggested alternatives. Hence, a higher number means a better unsafe-code-guidelines alternative or higher similarity.

unsafe-code-guidelines reviews and mentions

Posts with mentions or reviews of unsafe-code-guidelines. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2024-01-16.
  • 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

  • I wanna be a crab.
    16 projects | /r/rust | 27 Feb 2023
    C is much better specified than unsafe Rust. Some things are just not worked out yet in Rust. This may sometimes even bite very experienced devs, such as this issue with Box's aliasing semantics, which tripped up the author of left-right.
  • A note from our sponsor - InfluxDB
    www.influxdata.com | 26 Apr 2024
    Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality. Learn more →

Stats

Basic unsafe-code-guidelines repo stats
74
639
6.9
about 1 month ago

Sponsored
SaaSHub - Software Alternatives and Reviews
SaaSHub helps you find the best software and product alternatives
www.saashub.com