Skip to content

Unsafe fields #3458

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

Merged
traviscross merged 43 commits into from
Feb 1, 2026
+1,041 −0
Merged

Unsafe fields #3458

Changes from all commits
Commits
Show all changes
43 commits
Select commit Hold shift + click to select a range
63dea6b
Add unsafe fields RFC
jhpratt Jul 13, 2023
75528c0
RFC3458: Update Summary
jswrenn Jan 5, 2025
deafcc6
RFC3458: Update Motivation
jswrenn Jan 5, 2025
046969a
RFC3458: Introduce 'Rationale and Alternatives'
jswrenn Jan 5, 2025
a2f5d94
RFC3458: Update Guide-Level Explanation
jswrenn Jan 6, 2025
bb5b5a7
RFC3458: Require trivially droppable fields
jswrenn Jan 8, 2025
d21d32c
RFC3458: `Copy` is conditionally unsafe to implement
jswrenn Jan 8, 2025
7dda446
RFC3458: Update Reference-Level Explanation
jswrenn Jan 9, 2025
7351f0e
RFC3458: Alarm fatigue and its alternatives
jswrenn Jan 9, 2025
eb6969a
RFC3458: Reduce scope to additive invariants
jswrenn Feb 25, 2025
5167009
RFC3458: Add depth to 'Safe Unions' future possibility
jswrenn Feb 25, 2025
f14a6fd
RFC3458: Allow subtractive invariants by constraining safety hygiene
jswrenn Feb 26, 2025
cfea60f
RFC3458: Clarify that language safety invariants must never be violated
jswrenn Feb 26, 2025
0b678ca
RFC3458: Clarify that terminology used in RFC is unresolved.
jswrenn Feb 26, 2025
c848c59
RFC3458: Fix typos
jswrenn Feb 27, 2025
916feb4
RFC3458: Fields must be soundly droppable before being dropped
jswrenn Feb 28, 2025
667a3de
RFC3458: Add complete, realistic example
jswrenn Apr 2, 2025
21f38a1
RFC3458: Document why field copies and moves require `unsafe`
jswrenn Apr 2, 2025
b1b7aca
RFC3458: Explore 'Wrapper Type' and 'More Syntactic Granularity' alte…
jswrenn Apr 11, 2025
1932ace
RFC3458: Tweak `UniqueArc::arc` invariant.
jswrenn Apr 11, 2025
eaadc1e
RFC3458: Tweak `Sync` impl for `UniqueArc`
jswrenn Apr 11, 2025
e6cc51f
RFC3458: Remove problematic `Sync` impl
jswrenn Apr 15, 2025
6852c4c
RFC3458: Make `Unsafe::new` safe
jswrenn Apr 15, 2025
f9fd91b
RFC3458: Document 'Syntactic Knobs and Wrapper Types' as future possi…
jswrenn Apr 15, 2025
6ebe8a2
RFC3458: Clarify that syntactic knob possibility is not an easy migra…
jswrenn Apr 18, 2025
217dda6
RFC3458: Document trivial proof drawback's interaction with borrow ch…
jswrenn Apr 18, 2025
7617a81
RFC3458: Document alt of `Mixing Syntactic Knobs with a Wrapper Type`
jswrenn Apr 18, 2025
350ea73
RFC3458: Add links to RFC PR and Rust tracking issue
jswrenn Apr 18, 2025
1ec4c2d
RFC3458: Typo fix
jswrenn Apr 18, 2025
49e8e74
RFC3458: Clarify 'Syntactic Knobs and Wrapper Types' possibility
jswrenn May 29, 2025
78dc9ad
RFC3458: Clarify semantics in Reference-level explanation
jswrenn Jan 2, 2026
b3639de
RFC3458: Move RFC to `3458-unsafe-fields.md`
jswrenn Jan 2, 2026
c491b49
Clean up whitespace
traviscross Jan 27, 2026
21a659b
Fix typos in function name and struct name
traviscross Jan 27, 2026
1cad346
Fix whitespace and clarify prose in example
traviscross Jan 27, 2026
0857d93
Fix grammar issues
traviscross Jan 27, 2026
1e3a4bf
Fix additional grammar and consistency issues
traviscross Jan 27, 2026
0db5073
Fix hyphenation per AE conventions
traviscross Jan 27, 2026
64930d9
Use "that" for restrictive clauses
traviscross Jan 27, 2026
3e26be7
Replace "upon" with "on"
traviscross Jan 27, 2026
45c3c55
Replace "presently" with "currently"
traviscross Jan 27, 2026
816d4e7
Fix miscellaneous grammar issues
traviscross Jan 27, 2026
f5749ba
Fix heading levels
traviscross Jan 27, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Loading