-
Notifications
You must be signed in to change notification settings - Fork 59
Insights: rust-lang/unsafe-code-guidelines
Overview
-
0 Active pull requests
-
- 0 Merged pull requests
- 0 Open pull requests
- 1 Closed issue
- 2 New issues
There hasn’t been any commit activity on rust-lang/unsafe-code-guidelines in the last week.
Want to help out?
1 Issue closed by 1 person
-
Can the layouts of `Vec<i32>` and `Vec<u32>` guaranteed to be the same?
#560 closed
Mar 21, 2025
2 Issues opened by 2 people
-
Possible to interleave `&mut` and `&` safely?
#562 opened
Mar 25, 2025 -
Should values be well-typed?
#561 opened
Mar 24, 2025
6 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.
-
What about: Pointer-to-integer transmutes?
#286 commented on
Mar 20, 2025 • 0 new comments -
Promotion introduces UB into otherwise well-defined code
#493 commented on
Mar 20, 2025 • 0 new comments -
Stacked Borrows: How precise should UnsafeCell be tracked?
#236 commented on
Mar 20, 2025 • 0 new comments -
Removing allocations is technically unsound in OOM (out-of-memory) situations
#328 commented on
Mar 21, 2025 • 0 new comments -
Stabilize having the concept of "validity invariant" and "safety invariant"? Under which name?
#539 commented on
Mar 21, 2025 • 0 new comments -
Should we / can we make MaybeUninit<T> always preserve all bytes of T (including padding)?
#518 commented on
Mar 24, 2025 • 0 new comments