|
`DerefMove` vs `&move`
|
6
|
March 25, 2019
|
|
Proposal: reboot the Unsafe Code Guidelines team as a Working Group
|
24
|
March 25, 2019
|
|
Types as Contracts
|
119
|
March 25, 2019
|
|
Don't warn about nested unsafe blocks by default?
|
21
|
March 25, 2019
|
|
What does `unsafe` mean?
|
67
|
March 25, 2019
|
|
Idea to disallow multiple imports of a `-sys` crate
|
19
|
March 25, 2019
|
|
Disabling 'unsafe' by default
|
20
|
March 25, 2019
|
|
Support C APIs designed for safe unwinding
|
13
|
March 25, 2019
|
|
Rust 1.20 caused pinning to become incorrect
|
36
|
March 25, 2019
|
|
Role of UB / uninitialized memory
|
79
|
March 25, 2019
|
|
Taming Undefined Behavior in LLVM
|
7
|
March 25, 2019
|
|
Types as Contracts: Implementation and Evaluation
|
21
|
March 25, 2019
|
|
Rules for alignment and non-NULLness of references
|
22
|
March 25, 2019
|
|
Overflow checks and unsafe code
|
11
|
March 25, 2019
|
|
Next steps for the unsafe code guidelines
|
30
|
March 25, 2019
|
|
Canvas unsafe code in the wild
|
26
|
March 25, 2019
|
|
Blog post: Thoughts on trusting types and unsafe code
|
48
|
March 25, 2019
|
|
Unaligned SIMD (SSE2 in particular) loads/stores
|
5
|
March 25, 2019
|
|
Replace_with RFC
|
5
|
March 25, 2019
|
|
Pre-RFC: #[single_repr] attribute for ADTs
|
6
|
March 25, 2019
|
|
Notes on safe reachability for Rust
|
3
|
March 25, 2019
|
|
Blog post: observatonal equivalence and unsafe code
|
28
|
March 25, 2019
|
|
Unsafe code meetings?
|
3
|
March 25, 2019
|
|
Related Work Summaries
|
2
|
March 25, 2019
|
|
Organizing the rust-memory-model repo
|
4
|
March 25, 2019
|
|
Discussing high-level direction
|
7
|
March 25, 2019
|
|
Next steps for unsafe code guidelines
|
14
|
March 25, 2019
|
|
Tuple Slices
|
12
|
March 25, 2019
|
