about summary refs log tree commit diff
diff options
context:
space:
mode:
authorNiko Matsakis <niko@alum.mit.edu>2017-05-02 13:59:15 -0400
committerNiko Matsakis <niko@alum.mit.edu>2017-05-02 16:21:58 -0400
commit488b2a3e7b9d8a4c96f388dc7d8fdd2023ecc815 (patch)
tree81daf503a3368321625a7ab527235d1812911a64
parent25be7983e80bb1c370772ebbb97891d2030d68f0 (diff)
downloadrust-488b2a3e7b9d8a4c96f388dc7d8fdd2023ecc815.tar.gz
rust-488b2a3e7b9d8a4c96f388dc7d8fdd2023ecc815.zip
add FIXME to `Steal`
-rw-r--r--src/librustc/ty/steal.rs2
1 files changed, 2 insertions, 0 deletions
diff --git a/src/librustc/ty/steal.rs b/src/librustc/ty/steal.rs
index fd611266f08..0b081888881 100644
--- a/src/librustc/ty/steal.rs
+++ b/src/librustc/ty/steal.rs
@@ -29,6 +29,8 @@ use std::mem;
 /// Obviously, whenever you have a query that yields a `Steal` value,
 /// you must treat it with caution, and make sure that you know that
 /// -- once the value is stolen -- it will never be read from again.
+///
+/// FIXME(#41710) -- what is the best way to model linear queries?
 pub struct Steal<T> {
     value: RefCell<Option<T>>
 }