Skip to content

Issues: rust-lang/unsafe-code-guidelines

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Author
Filter by author
Loading
Label
Filter by label
Loading
Use alt + click/return to exclude labels
or + click/return for logical OR
Projects
Filter by project
Loading
Milestones
Filter by milestone
Loading
Assignee
Filter by who’s assigned
Assigned to nobody Loading
Sort

Issues list

How does UnsafeCell interact with match; can op.sem ensure exhaustiveness? A-aliasing-model Topic: Related to the aliasing model (e.g. Stacked/Tree Borrows) A-optimization Category: Discussing optimizations we might (not) want to support C-open-question Category: An open question that we should revisit S-pending-design Status: Resolving this issue requires addressing some open design questions
#399 opened Apr 16, 2023 by chorman0773
Should 'dereferenceable' take into account the dynamic size information where possible? C-open-question Category: An open question that we should revisit
#374 opened Nov 2, 2022 by RalfJung
Should drop_in_place imply dereferencability? C-open-question Category: An open question that we should revisit
#373 opened Nov 2, 2022 by JakobDegen
Stacked Borrows: do we even want protectors? A-aliasing-model Topic: Related to the aliasing model (e.g. Stacked/Tree Borrows) A-dereferenceable Topic: when exactly does a reference need to point to regular dereferenceable memory? C-open-question Category: An open question that we should revisit
#372 opened Oct 29, 2022 by RalfJung
Stacked Borrows: aliasing rules for local variables A-aliasing-model Topic: Related to the aliasing model (e.g. Stacked/Tree Borrows) C-open-question Category: An open question that we should revisit
#363 opened Sep 18, 2022 by RalfJung
What about: mixed-size atomic accesses C-open-question Category: An open question that we should revisit
#345 opened Jul 2, 2022 by RalfJung
Do function pointers behave like data pointers (wrt provenance and other aspects)? A-provenance Topic: Related to when which values have which provenance (but not which alias restrictions follow) C-open-question Category: An open question that we should revisit
#340 opened May 24, 2022 by RalfJung
What about: Pointer-to-integer transmutes? A-provenance Topic: Related to when which values have which provenance (but not which alias restrictions follow) C-open-question Category: An open question that we should revisit
#286 opened Jun 7, 2021 by RalfJung
Are statics confined to the size indicated by their type? A-memory Topic: Related to memory accesses C-open-question Category: An open question that we should revisit
#259 opened Nov 28, 2020 by RalfJung
Storing an object as &Header, but reading the data past the end of the header A-aliasing-model Topic: Related to the aliasing model (e.g. Stacked/Tree Borrows) A-SB-vs-TB Topic: Design questions where SB and TB are opposite sides of the design axis C-open-question Category: An open question that we should revisit
#256 opened Nov 11, 2020 by thomcc
Validity of ManuallyDrop, or: ManuallyDrop<Box<_>> is strange A-validity Topic: Related to validity invariants C-open-question Category: An open question that we should revisit
#245 opened Aug 12, 2020 by RalfJung
What about: splitting struct into separate fields despite escaped references (maybe even raw pointers) A-aliasing-model Topic: Related to the aliasing model (e.g. Stacked/Tree Borrows) A-memory Topic: Related to memory accesses A-optimization Category: Discussing optimizations we might (not) want to support C-open-question Category: An open question that we should revisit
#244 opened Aug 6, 2020 by RalfJung
Semver guarantees for data layouts A-layout Topic: Related to data structure layout (`#[repr]`) C-open-question Category: An open question that we should revisit
#242 opened Jul 28, 2020 by the8472
Stacked Borrows: How precise should UnsafeCell be tracked? A-aliasing-model Topic: Related to the aliasing model (e.g. Stacked/Tree Borrows) A-SB-vs-TB Topic: Design questions where SB and TB are opposite sides of the design axis C-open-question Category: An open question that we should revisit
#236 opened Jun 12, 2020 by RalfJung
Layout of pointers to slices of ZSTs A-layout Topic: Related to data structure layout (`#[repr]`) C-open-question Category: An open question that we should revisit
#224 opened Jan 9, 2020 by gnzlbg
Should Rust assume that there are unknown threads of execution? A-abstract-machine Topic: concerning the abstract machine in general (as opposed to any specific part of it) C-open-question Category: An open question that we should revisit
#215 opened Oct 18, 2019 by gnzlbg
When are things guaranteed to have unique addresses? A-pointer-equality Topic: Related to questions of pointer equality/identity C-open-question Category: An open question that we should revisit S-pending-design Status: Resolving this issue requires addressing some open design questions
#206 opened Sep 20, 2019 by comex
Multiple incompatible function declarations A-ffi Topic: Related to FFI C-open-question Category: An open question that we should revisit S-pending-design Status: Resolving this issue requires addressing some open design questions Triaged Visited during a backlog bonanza meeting
#198 opened Aug 27, 2019 by gnzlbg
Mutable references vs self-referential structs A-aliasing-model Topic: Related to the aliasing model (e.g. Stacked/Tree Borrows) C-open-question Category: An open question that we should revisit S-pending-design Status: Resolving this issue requires addressing some open design questions
#148 opened Jun 21, 2019 by RalfJung
What about: use-after-move and (maybe) use-after-drop A-memory Topic: Related to memory accesses A-uninitialized Topic: Related to uninitialized memory C-open-question Category: An open question that we should revisit S-pending-design Status: Resolving this issue requires addressing some open design questions
#188 opened May 31, 2019 by RalfJung
Stacked Borrows: raw pointer usable only for T too strict? A-aliasing-model Topic: Related to the aliasing model (e.g. Stacked/Tree Borrows) A-SB-vs-TB Topic: Design questions where SB and TB are opposite sides of the design axis C-open-question Category: An open question that we should revisit S-pending-design Status: Resolving this issue requires addressing some open design questions
#134 opened May 28, 2019 by RalfJung
Stacked Borrows: asserting uniqueness too early? Should we allow the optimizer to add spurious stores? A-aliasing-model Topic: Related to the aliasing model (e.g. Stacked/Tree Borrows) A-SB-vs-TB Topic: Design questions where SB and TB are opposite sides of the design axis C-open-question Category: An open question that we should revisit S-pending-design Status: Resolving this issue requires addressing some open design questions
#133 opened May 28, 2019 by RalfJung
Layout of char A-layout Topic: Related to data structure layout (`#[repr]`) C-open-question Category: An open question that we should revisit S-not-opsem Despite being in this repo, this is not primarily a T-opsem question
#101 opened Mar 15, 2019 by gnzlbg
What about: invalid not-used-again values? Is "validity on typed copy" enough? A-validity Topic: Related to validity invariants C-open-question Category: An open question that we should revisit S-pending-design Status: Resolving this issue requires addressing some open design questions
#84 opened Feb 6, 2019 by RalfJung
Layout of single-variant enums A-layout Topic: Related to data structure layout (`#[repr]`) C-open-question Category: An open question that we should revisit S-not-opsem Despite being in this repo, this is not primarily a T-opsem question T-lang
#79 opened Jan 10, 2019 by nikomatsakis
ProTip! What’s not been updated in a month: updated:<2025-04-30.