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.

Sign up for GitHub

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

Clear current search query, filters, and sorts
7 Open 7 Closed
7 Open 7 Closed
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
Sort
Sort by
Newest Oldest Most commented Least commented Recently updated Least recently updated Best match
Most reactions
👍 👎 😄 🎉 😕 ❤️ 🚀 👀

Issues list

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
24
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
19
What about: volatile, concurrency, and interaction with untrusted threads A-memory Topic: Related to memory accesses C-open-question Category: An open question that we should revisit Triaged Visited during a backlog bonanza meeting
#152 opened Jun 25, 2019 by hsivonen
127
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
40
What about: Targets where NULL is a valid pointer A-memory Topic: Related to memory accesses A-validity Topic: Related to validity invariants S-pending-design Status: Resolving this issue requires addressing some open design questions
#29 opened Sep 18, 2018 by RalfJung
53
What about: Virtual memory effects A-memory Topic: Related to memory accesses S-pending-design Status: Resolving this issue requires addressing some open design questions
#28 opened Sep 18, 2018 by RalfJung
10
I need to do an oob vector load. How? A-memory Topic: Related to memory accesses S-pending-design Status: Resolving this issue requires addressing some open design questions
#2 opened Jul 5, 2018 by brson
67
ProTip! Updated in the last three days: updated:>2025-05-09.