---

yaml
---
r: 31459
b: refs/heads/dist-snap
c: 73ca560
h: refs/heads/master
i:
  31457: 1fd1fdc
  31455: 6309c00
v: v3

Author: bblum

[refs]

@@ -7,6 +7,6 @@ refs/tags/release-0.1: 1f5c5126e96c79d22cb7862f75304136e204f105
 refs/heads/ndm: f3868061cd7988080c30d6d5bf352a5a5fe2460b
 refs/heads/try2: d0c6ce338884ee21843f4b40bf6bf18d222ce5df
 refs/heads/incoming: d9317a174e434d4c99fc1a37fd7dc0d2f5328d37
-refs/heads/dist-snap: 3c731df890e4354fbd30a7a4a21f0352ac6f3102
+refs/heads/dist-snap: 73ca5603bd1bf57e1734ff859299d7b10626a644
 refs/tags/release-0.2: c870d2dffb391e14efb05aa27898f1f6333a9596
 refs/tags/release-0.3: b5f0d0f648d9a6153664837026ba1be43d3e2503

branches/dist-snap/src/libcore/task.rs

@@ -945,8 +945,13 @@ fn spawn_raw(opts: task_opts, +f: fn~()) {
  * task-local data slot (and use class destructors, not code inside the
  * function, if specific teardown is needed). DO NOT use multiple
  * instantiations of a single polymorphic function to index data of different
- * types; arbitrary type coercion is possible this way. The interface is safe
- * as long as all key functions are monomorphic.
+ * types; arbitrary type coercion is possible this way.
+ *
+ * One other exception is that this global state can be used in a destructor
+ * context to create a circular @-box reference, which will crash during task
+ * failure (see issue #3039).
+ *
+ * These two cases aside, the interface is safe.
  */
 type local_data_key<T: owned> = fn@(+@T);