language design   Unsafe Code Guidelines


About the Unsafe Code Guidelines category (1)
Explicitly marking unsafe macro expressions (17)
Re: `Pin` from `&mut` refs (19)
Unsafe code annotations (16)
Barriers and Two-phase Borrows in Stacked Borrows (5)
Writing through a pointer derived from a shared reference, after that reference is dead (7)
Bit-wise reasoning for atomic accesses ( 2 ) (36)
Stacked Borrows Implemented (16)
FFI mutating raw pointer where immutable reference in scope, is this UB? (9)
Unsafe Code Guidelines Meetings (8)
Stacked Borrows: An Aliasing Model For Rust ( 2 3 ) (49)
Is it possible to be memory-safe with deallocated `*self`? (20)
Two Kinds of Invariants: Safety and Validity ( 2 ) (27)
Reordering of writes via differently-typed pointers (14)
Proposal for Unsafe Code Guidelines process (9)
`DerefMove` vs `&move` (5)
Proposal: reboot the Unsafe Code Guidelines team as a Working Group ( 2 ) (23)
Types as Contracts ( 2 3 4 5 6 ) (118)
Don't warn about nested unsafe blocks by default? (20)
What does `unsafe` mean? ( 2 3 4 ) (66)
Idea to disallow multiple imports of a `-sys` crate (18)
Disabling 'unsafe' by default (19)
Support C APIs designed for safe unwinding (12)
Rust 1.20 caused pinning to become incorrect ( 2 ) (35)
Role of UB / uninitialized memory ( 2 3 4 ) (78)
Taming Undefined Behavior in LLVM (6)
Types as Contracts: Implementation and Evaluation (20)
Rules for alignment and non-NULLness of references ( 2 ) (21)
Overflow checks and unsafe code (10)
Next steps for the unsafe code guidelines ( 2 ) (29)