From 818ac082d211128d399b51f1466f9fac1bbe4b43 Mon Sep 17 00:00:00 2001
From: "Felix S. Klock II" <pnkfelix@pnkfx.org>
Date: Mon, 17 Oct 2016 16:17:54 +0200
Subject: [PATCH] remove fixme that i no longer think appropriate.

---
 src/librustc_typeck/check/dropck.rs | 11 -----------
 1 file changed, 11 deletions(-)

diff --git a/src/librustc_typeck/check/dropck.rs b/src/librustc_typeck/check/dropck.rs
index 607b32fd1402..03842f3a0a05 100644
--- a/src/librustc_typeck/check/dropck.rs
+++ b/src/librustc_typeck/check/dropck.rs
@@ -510,17 +510,6 @@ enum DropckKind<'tcx> {
     /// outlive self.
     ///
     /// Equivalent to RevisedTy with no change to the self type.
-    ///
-    /// FIXME: this name may not be general enough; it should be
-    /// talking about Phantom lifetimes rather than just borrows.
-    ///
-    /// (actually, pnkfelix is not 100% sure that's the right
-    /// viewpoint.  If I'm holding a phantom lifetime just to
-    /// constrain a reference type that occurs solely in *negative*
-    /// type positions, then my destructor cannot itself ever actually
-    /// access such references, right? And don't we end up essentially
-    /// requring people to put a fake borrow inside a PhantomData in
-    /// order to make phantom lifetimes work anyway?)
     BorrowedDataMustStrictlyOutliveSelf,
 
     /// The nearly completely-unsafe kind.