Skip to content

Commit 572f23b

Browse files
committed
fix wording
1 parent 2077313 commit 572f23b

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

text/0000-maybe-dangling.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -256,7 +256,7 @@ Notice that `UnsafeCell` acts "behind references" while `MaybeDangling`, like `M
256256
[unresolved-questions]: #unresolved-questions
257257

258258
- What should the type be called?
259-
`MaybeDangling` is somewhat misleading since the safety invariant still requires everything to be dereferenceable, only the requirement of dereferencability and noalias is relaxed.
259+
`MaybeDangling` is somewhat misleading since the *safety* invariant still requires everything to be dereferenceable, only the *validity* requirement of dereferenceability and noalias is relaxed.
260260
This is a bit like `ManuallyDrop` which supports dropping via an `unsafe` function but its safety invariant says that the data is not dropped (so that it can implement `Deref` and `DerefMut` and a safe `into_inner`).
261261
Furthermore, the type also allows maybe-aliasing references, not just maybe-dangling references.
262262
Other possible names might be things like `InertPointers` or `SuspendedPointers`.

0 commit comments

Comments
 (0)