From 8f6451a364f27197de45d5ecfd90901aab291687 Mon Sep 17 00:00:00 2001
From: Daniel Henry-Mantilla <daniel.henry.mantilla@gmail.com>
Date: Mon, 7 Aug 2023 20:26:08 +0200
Subject: [PATCH] Add non-`#[may_dangle]` mention to dropck mechanic

---
 src/phantom-data.md | 5 +++++
 1 file changed, 5 insertions(+)

diff --git a/src/phantom-data.md b/src/phantom-data.md
index c82859e6..cd2428d9 100644
--- a/src/phantom-data.md
+++ b/src/phantom-data.md
@@ -110,6 +110,11 @@ When a type already has a `Drop impl`, **adding an extra `_owns_T: PhantomData<T
 is thus _superfluous_ and accomplishes nothing**, dropck-wise (it still affects variance
 and auto-traits).
 
+  - (advanced edge case: if the type containing the `PhantomData` has no `Drop` impl at all,
+    but still has drop glue (by having _another_ field with drop glue), then the
+    dropck/`#[may_dangle]` considerations mentioned herein do apply as well: a `PhantomData<T>`
+    field will then require `T` to be droppable whenever the containing type goes out of scope).
+
 ___
 
 But this situation can sometimes lead to overly restrictive code. That's why the