From e4fdbcbc9fdc7c3e1670e5c981acbf013ffa51bc Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?John=20K=C3=A5re=20Alsaker?= <john.kare.alsaker@gmail.com>
Date: Sat, 15 Jul 2017 04:33:45 +0200
Subject: [PATCH] Update FIXME

---
 src/librustc_typeck/check/closure.rs | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/src/librustc_typeck/check/closure.rs b/src/librustc_typeck/check/closure.rs
index 0f68b1597784..7e7e1018f977 100644
--- a/src/librustc_typeck/check/closure.rs
+++ b/src/librustc_typeck/check/closure.rs
@@ -32,7 +32,8 @@ impl<'a, 'gcx, 'tcx> FnCtxt<'a, 'gcx, 'tcx> {
         debug!("check_expr_closure(expr={:?},expected={:?})",
                expr,
                expected);
-        // FIXME: See if expected_kind here can impact generators
+        // FIXME: Should we adapt deduce_expectations_from_expected_type to work with
+        // generator traits? It looks like it's conservative to add support for this later.
 
         // It's always helpful for inference if we know the kind of
         // closure sooner rather than later, so first examine the expected