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