rust-lang/unsafe-code-guidelines

Stacked Borrows and Tree Borrows both currently allow overlapping mutable references to be used, as long as they don't access the same memory

A-aliasing-model

#576

· ais523 opened

on Jun 23, 2025

3

Strengthening TB so that we can discard SB

A-aliasing-model

#573

· RalfJung opened

on Jun 9, 2025

2

Aliasing-motivated concurrency optimizations

#572

· gonzalobg opened

on Jun 7, 2025

1

`'static` reference to local variable that never goes out of scope?

#565

· joshlf opened

on Apr 3, 2025

10

What is the operational spec for `use` expressions?

#564

· RalfJung opened

on Mar 31, 2025

Possible to interleave `&mut` and `&` safely?

#562

· joshlf opened

on Mar 25, 2025

8

Do the bytes of a pointer have to stay in the same order?

A-provenance

#558

· RalfJung opened

on Feb 20, 2025

3

Copy propagation on "move" assignments introduces UB (using Miri/MiniRust semantics)

#556

· RalfJung opened

on Feb 13, 2025

2

How to explain linker symbols used as integers (and not pointers to an allocation)?

#554

· ia0 opened

on Feb 4, 2025

4

"Any two types with size 0 and alignment 1 are ABI-compatible" vs the Windows ABI

#552

· RalfJung opened

on Jan 10, 2025

23

Does the Allocator API allow sending pointer ownership across an FFI boundary?

#550

· not-an-aardvark opened

on Jan 3, 2025

1

What are the preconditions for (overlapping) `ptr::copy`?

#549

· steffahn opened

on Dec 17, 2024

1

10

Our concurrency memory model (inherited from C++20) is incompatible with x86

#548

· RalfJung opened

on Dec 9, 2024

28

Wait, how does placing ZST statics work again?

#546

· workingjubilee opened

on Nov 8, 2024

What about: distributed slices (linkme)

#545

· CAD97 opened

on Nov 8, 2024

3

Where does one instance of the Rust Abstract Machine end and another one start?

#543

· VorpalBlade opened

on Oct 31, 2024

19

Will destructors create `&mut` references only when `Drop::drop()` is called?

#542

· theemathas opened

on Oct 30, 2024

2

Are long-lived references to thread_local variables allowed?

#541

· theemathas opened

on Oct 27, 2024

4

Is pattern evaluation order guaranteed?

#540

· zachs18 opened

on Oct 26, 2024

Stabilize having the concept of "validity invariant" and "safety invariant"? Under which name?

#539

· RalfJung opened

on Oct 18, 2024

90

How can I tell the Rust compiler `&mut [u8]` has changed after a DMA operation

#537

· schultetwin1 opened

on Oct 7, 2024

41

What are the special magic rules around `malloc`?

#535

· RalfJung opened

on Oct 6, 2024

9

Minimum guarantees for union construction and typed copies?

#533

· joshlf opened

on Oct 2, 2024

1

What about: aliasing requirements for nested references?

A-aliasing-model

#532

· oxalica opened

on Sep 28, 2024

5

Can FFI code use `memory_order_consume`

#528

· chorman0773 opened

on Aug 17, 2024

9

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

Stacked Borrows and Tree Borrows both currently allow overlapping mutable references to be used, as long as they don't access the same memory

Strengthening TB so that we can discard SB

Aliasing-motivated concurrency optimizations

`'static` reference to local variable that never goes out of scope?

What is the operational spec for `use` expressions?

Possible to interleave `&mut` and `&` safely?

Do the bytes of a pointer have to stay in the same order?

Copy propagation on "move" assignments introduces UB (using Miri/MiniRust semantics)

How to explain linker symbols used as integers (and not pointers to an allocation)?

"Any two types with size 0 and alignment 1 are ABI-compatible" vs the Windows ABI

Does the Allocator API allow sending pointer ownership across an FFI boundary?

What are the preconditions for (overlapping) `ptr::copy`?

Our concurrency memory model (inherited from C++20) is incompatible with x86

Wait, how does placing ZST statics work again?

What about: distributed slices (linkme)

Where does one instance of the Rust Abstract Machine end and another one start?

Will destructors create `&mut` references only when `Drop::drop()` is called?

Are long-lived references to thread_local variables allowed?

Is pattern evaluation order guaranteed?

Stabilize having the concept of "validity invariant" and "safety invariant"? Under which name?

How can I tell the Rust compiler `&mut [u8]` has changed after a DMA operation

What are the special magic rules around `malloc`?

Minimum guarantees for union construction and typed copies?

What about: aliasing requirements for nested references?

Can FFI code use `memory_order_consume`

Issues

Search results