Clean up unfinished portions of task tutorial

This commit is contained in:
Brian Anderson 2012-10-07 21:29:26 -07:00
parent 0e7571b060
commit f5c3af1c1a

View File

@ -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