---

yaml
---
r: 31093
b: refs/heads/incoming
c: f5c3af1
h: refs/heads/master
i:
  31091: 37e7279
v: v3

Author: brson

[refs]

@@ -6,7 +6,7 @@ refs/heads/try: d324a424d8f84b1eb049b12cf34182bda91b0024
 refs/tags/release-0.1: 1f5c5126e96c79d22cb7862f75304136e204f105
 refs/heads/ndm: f3868061cd7988080c30d6d5bf352a5a5fe2460b
 refs/heads/try2: d0c6ce338884ee21843f4b40bf6bf18d222ce5df
-refs/heads/incoming: 0e7571b0607ee3920a2d29eee35fdf9e7e92442c
+refs/heads/incoming: f5c3af1c1ab18632d2e8aa6c3a5fe369e670a471
 refs/heads/dist-snap: 2f32a1581f522e524009138b33b1c7049ced668d
 refs/tags/release-0.2: c870d2dffb391e14efb05aa27898f1f6333a9596
 refs/tags/release-0.3: b5f0d0f648d9a6153664837026ba1be43d3e2503

branches/incoming/doc/tutorial-tasks.md

@@ -36,6 +36,8 @@ explore some typical patterns in concurrent Rust code, and finally
 discuss some of the more exotic synchronization types in the standard
 library.
 
+> ***Warning:*** This tutorial is incomplete
+
 ## A note about the libraries
 
 While Rust's type system provides the building blocks needed for safe
@@ -295,8 +297,6 @@ let result = ports.foldl(0, |accum, port| *accum + port.recv() );
 # fn some_expensive_computation(_i: uint) -> int { 42 }
 ~~~
 
-# TODO
-
 # Handling task failure
 
 Rust has a built-in mechanism for raising exceptions, written `fail`
@@ -451,13 +451,6 @@ fail;
 # };
 ~~~
 
-
-# Unfinished notes
-
-## Actor patterns
-
-## Linearity, option dancing, owned closures
-
 ## Creating a task with a bi-directional communication path
 
 A very common thing to do is to spawn a child task where the parent