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