-
Notifications
You must be signed in to change notification settings - Fork 61
Insights: rust-lang/unsafe-code-guidelines
Overview
-
0 Active pull requests
-
- 0 Merged pull requests
- 0 Open pull requests
- 2 Closed issues
- 0 New issues
There hasn’t been any commit activity on rust-lang/unsafe-code-guidelines in the last month.
Want to help out?
2 Issues closed by 2 people
-
How can I tell the Rust compiler `&mut [u8]` has changed after a DMA operation
#537 closed
Jul 23, 2025 -
What about: Targets where NULL is a valid pointer
#29 closed
Jul 21, 2025
8 Unresolved conversations
Sometimes conversations happen on old items that aren’t yet closed. Here is a list of all the Issues and Pull Requests with unresolved conversations.
-
Document (for the purpose of education) cases where Rust gives unsafe code fewer guarantees than C/C++ code has come to rely on
#294 commented on
Jul 4, 2025 • 0 new comments -
What are the values of a union type? (in particular, what is the validity invariant of a union)
#438 commented on
Jul 22, 2025 • 0 new comments -
## Pre-Pre-RFC: `core::arch::{load, store}` and stricter volatile semantics
#321 commented on
Jul 24, 2025 • 0 new comments -
Should validity of a reference depend on the *contents* of memory in any way?
#414 commented on
Jul 25, 2025 • 0 new comments -
Can references to uninhabited types ever be valid?
#413 commented on
Jul 25, 2025 • 0 new comments -
Is Changing the Floating-point environment for intrinsic/assembly code UB?
#471 commented on
Jul 29, 2025 • 0 new comments -
`repr(C)`/`extern "C"` does not always match the current target's C toolchain (affects msvc, aix)
#521 commented on
Aug 1, 2025 • 0 new comments -
Layout and behavior of enums with uninhabited fields in some variants
#443 commented on
Aug 1, 2025 • 0 new comments