Search results

Are statics confined to the size indicated by their type?

A-memoryTopic: Related to memory accessesTopic: Related to memory accesses

C-open-questionCategory: An open question that we should revisitCategory: An open question that we should revisit

Status: Open.

#259 In rust-lang/unsafe-code-guidelines;

· RalfJung opened on Nov 28, 2020

What about: splitting struct into separate fields despite escaped references (maybe even raw pointers)

A-aliasing-modelTopic: Related to the aliasing model (e.g. Stacked/Tree Borrows)Topic: Related to the aliasing model (e.g. Stacked/Tree Borrows)

A-memoryTopic: Related to memory accessesTopic: Related to memory accesses

A-optimizationCategory: Discussing optimizations we might (not) want to supportCategory: Discussing optimizations we might (not) want to support

C-open-questionCategory: An open question that we should revisitCategory: An open question that we should revisit

Status: Open.

#244 In rust-lang/unsafe-code-guidelines;

· RalfJung opened on Aug 6, 2020

What about: use-after-move and (maybe) use-after-drop

A-memoryTopic: Related to memory accessesTopic: Related to memory accesses

A-uninitializedTopic: Related to uninitialized memoryTopic: Related to uninitialized memory

C-open-questionCategory: An open question that we should revisitCategory: An open question that we should revisit

S-pending-designStatus: Resolving this issue requires addressing some open design questionsStatus: Resolving this issue requires addressing some open design questions

Status: Open.

#188 In rust-lang/unsafe-code-guidelines;

· RalfJung opened on May 31, 2019

What about: Targets where NULL is a valid pointer

A-memoryTopic: Related to memory accessesTopic: Related to memory accesses

A-validityTopic: Related to validity invariantsTopic: Related to validity invariants

S-pending-designStatus: Resolving this issue requires addressing some open design questionsStatus: Resolving this issue requires addressing some open design questions

Status: Open.

#29 In rust-lang/unsafe-code-guidelines;

· RalfJung opened on Sep 18, 2018

What about: Virtual memory effects

A-memoryTopic: Related to memory accessesTopic: Related to memory accesses

S-pending-designStatus: Resolving this issue requires addressing some open design questionsStatus: Resolving this issue requires addressing some open design questions

Status: Open.

#28 In rust-lang/unsafe-code-guidelines;

· RalfJung opened on Sep 18, 2018

I need to do an oob vector load. How?

A-memoryTopic: Related to memory accessesTopic: Related to memory accesses

S-pending-designStatus: Resolving this issue requires addressing some open design questionsStatus: Resolving this issue requires addressing some open design questions

Status: Open.

#2 In rust-lang/unsafe-code-guidelines;

· brson opened on Jul 5, 2018