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

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
45
Clarify the definition of undefined behavior A-abstract-machine Topic: concerning the abstract machine in general (as opposed to any specific part of it) C-terminology Category: Discussing terminology -- which term to use, how to define it, adding it to the glossary S-pending-documentation Status: The issue is "resolved," but this resolution needs documentation Triaged Visited during a backlog bonanza meeting
#202 opened Sep 11, 2019 by gnzlbg
44
Glossary unspecified/implementation-defined behavior A-abstract-machine Topic: concerning the abstract machine in general (as opposed to any specific part of it) C-terminology Category: Discussing terminology -- which term to use, how to define it, adding it to the glossary Triaged Visited during a backlog bonanza meeting
#201 opened Sep 11, 2019 by gnzlbg
10
ProTip! Add no:assignee to see everything that’s not assigned.