diff options
| author | bors <bors@rust-lang.org> | 2013-08-28 12:30:52 -0700 |
|---|---|---|
| committer | bors <bors@rust-lang.org> | 2013-08-28 12:30:52 -0700 |
| commit | 9c33ef5a7c24abe258be5c130dec1c77e72de86b (patch) | |
| tree | e804dbd8a8bf008fa2d26394d3832a504cbd5ede | |
| parent | 64ed3721f74c699d931e1d5ccf41d5db7cea0218 (diff) | |
| parent | d923f75d79836ef281be8efaecb958dc50af161d (diff) | |
| download | rust-9c33ef5a7c24abe258be5c130dec1c77e72de86b.tar.gz rust-9c33ef5a7c24abe258be5c130dec1c77e72de86b.zip | |
auto merge of #8828 : brson/rust/randomness, r=thestinger
The new scheduler is not currently that random.
| -rw-r--r-- | doc/tutorial-tasks.md | 15 |
1 files changed, 0 insertions, 15 deletions
diff --git a/doc/tutorial-tasks.md b/doc/tutorial-tasks.md index d190c332e66..18f35cf39a8 100644 --- a/doc/tutorial-tasks.md +++ b/doc/tutorial-tasks.md @@ -113,21 +113,6 @@ do spawn { } ~~~ -By default, the scheduler multiplexes tasks across the available cores, running -in parallel. Thus, on a multicore machine, running the following code -should interleave the output in vaguely random order. - -~~~ -# use std::io::print; -# use std::task::spawn; - -for child_task_number in range(0, 20) { - do spawn { - print(fmt!("I am child number %d\n", child_task_number)); - } -} -~~~ - ## Communication Now that we have spawned a new task, it would be nice if we could |
