user0/rust
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

remove fixme that i no longer think appropriate.

Browse source
This commit is contained in:
Felix S. Klock II 2016-10-17 16:17:54 +02:00
parent 0271a9a60a
commit 818ac082d2
1 changed files with 0 additions and 11 deletions
Download patch file Download diff file Expand all files Collapse all files

11
src/librustc_typeck/check/dropck.rs
View file

@ -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.