|
About the Unsafe Code Guidelines category
|
2
|
March 25, 2019
|
|
Valgrind/Memcheck false positive fixes for Rust
|
2
|
October 22, 2019
|
|
Computing raw pointers to fields
|
3
|
October 21, 2019
|
|
`unordered` as a solution to "Bit-wise reasoning for atomic accesses"
|
24
|
October 15, 2019
|
|
Make mem::uninitialized and mem::zeroed panic for (some) types where 0 is a niche
|
30
|
August 16, 2019
|
|
Enum size overflow detection
|
9
|
August 1, 2019
|
|
Fake static
|
2
|
July 28, 2019
|
|
Official document that states "references must point to initialized data"?
|
41
|
July 17, 2019
|
|
[Idea?] Access state for borrowing
|
27
|
July 1, 2019
|
|
[Idea] Pointer to Field
|
82
|
September 3, 2019
|
|
Safety of structurally unpinned closures
|
6
|
May 27, 2019
|
|
Can `Pin::map_unchecked_mut` actually be used safely at all?
|
8
|
August 22, 2019
|
|
Stacked Borrows 2
|
8
|
May 21, 2019
|
|
[Solved] Trait object vtables and the Any trait
|
4
|
May 2, 2019
|
|
Unsafe Code Guidelines Meetings
|
10
|
June 10, 2019
|
|
Bit-wise reasoning for atomic accesses
|
40
|
May 25, 2019
|
|
Explicitly marking unsafe macro expressions
|
18
|
May 21, 2019
|
|
Re: `Pin` from `&mut` refs
|
20
|
May 21, 2019
|
|
Unsafe code annotations
|
17
|
April 21, 2019
|
|
Barriers and Two-phase Borrows in Stacked Borrows
|
6
|
March 28, 2019
|
|
Writing through a pointer derived from a shared reference, after that reference is dead
|
8
|
March 27, 2019
|
|
Stacked Borrows Implemented
|
17
|
March 25, 2019
|
|
FFI mutating raw pointer where immutable reference in scope, is this UB?
|
10
|
March 25, 2019
|
|
Stacked Borrows: An Aliasing Model For Rust
|
50
|
March 25, 2019
|
|
Is it possible to be memory-safe with deallocated `*self`?
|
21
|
March 25, 2019
|
|
Two Kinds of Invariants: Safety and Validity
|
28
|
March 25, 2019
|
|
Reordering of writes via differently-typed pointers
|
15
|
March 25, 2019
|
|
Proposal for Unsafe Code Guidelines process
|
10
|
March 25, 2019
|
|
`DerefMove` vs `&move`
|
6
|
March 25, 2019
|
|
Proposal: reboot the Unsafe Code Guidelines team as a Working Group
|
24
|
March 25, 2019
|
