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
2 Open 3 Closed
2 Open 3 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

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
5
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
ProTip! no:milestone will show everything without a milestone.