---

yaml
---
r: 35761
b: refs/heads/try2
c: f5c3af1
h: refs/heads/master
i:
  35759: 92d3cdb
v: v3

Author: brson

[refs]

@@ -5,7 +5,7 @@ refs/heads/snap-stage3: eb8fd119c65c67f3b1b8268cc7341c22d39b7b61
 refs/heads/try: d324a424d8f84b1eb049b12cf34182bda91b0024
 refs/tags/release-0.1: 1f5c5126e96c79d22cb7862f75304136e204f105
 refs/heads/ndm: f3868061cd7988080c30d6d5bf352a5a5fe2460b
-refs/heads/try2: 0e7571b0607ee3920a2d29eee35fdf9e7e92442c
+refs/heads/try2: f5c3af1c1ab18632d2e8aa6c3a5fe369e670a471
 refs/heads/incoming: d9317a174e434d4c99fc1a37fd7dc0d2f5328d37
 refs/heads/dist-snap: 22efa39382d41b084fde1719df7ae8ce5697d8c9
 refs/tags/release-0.2: c870d2dffb391e14efb05aa27898f1f6333a9596

branches/try2/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