---

yaml
---
r: 24033
b: refs/heads/master
c: 7bf0aa1
h: refs/heads/master
i:
  24031: 7b4b51c
v: v3

Author: brson

[refs]

@@ -1,5 +1,5 @@
 ---
-refs/heads/master: cfed923600e2f7ad34241501200d595abccdeb54
+refs/heads/master: 7bf0aa1c4367fd6904f68457233c360dafb27a93
 refs/heads/snap-stage1: e33de59e47c5076a89eadeb38f4934f58a3618a6
 refs/heads/snap-stage3: cd6f24f9d14ac90d167386a56e7a6ac1f0318195
 refs/heads/try: ffbe0e0e00374358b789b0037bcb3a577cd218be

trunk/src/libcore/core.rc

@@ -10,12 +10,14 @@ used features.
 `core` includes modules corresponding to each of the integer types, each of
 the floating point types, the `bool` type, tuples, characters, strings,
 vectors (`vec`), shared boxes (`box`), and unsafe and borrowed pointers
-(`ptr`).  Additionally, `core` provides very commonly used built-in types
-and operations, concurrency primitives, platform abstractions, I/O, and
-complete bindings to the C standard library.
-
-`core` is linked to all crates and its contents imported.  Implicitly, all
-crates behave as if they included the following prologue:
+(`ptr`).  Additionally, `core` provides task management and creation (`task`),
+communication primitives (`comm` and `pipes`), an efficient vector builder
+(`dvec`), platform abstractions (`os` and `path`), basic I/O abstractions
+(`io`), common traits (`cmp`, `num`, `to_str`), and complete bindings
+to the C standard library (`libc`).
+
+`core` is linked to all crates by default and its contents imported.
+Implicitly, all crates behave as if they included the following prologue:
 
     extern mod core;
     use core::*;

trunk/src/libcore/task.rs

@@ -82,8 +82,6 @@ macro_rules! move_it (
     { $x:expr } => { unsafe { let y <- *ptr::addr_of($x); move y } }
 )
 
-/* Data types */
-
 /// A handle to a task
 enum Task {
     TaskHandle(task_id)
@@ -800,7 +798,7 @@ unsafe fn atomically<U>(f: fn() -> U) -> U {
     f()
 }
 
-/****************************************************************************
+/* **************************************************************************
  * Spawning & linked failure
  *
  * Several data structures are involved in task management to allow properly
@@ -1431,7 +1429,7 @@ fn spawn_raw(+opts: TaskOpts, +f: fn~()) {
     }
 }
 
-/****************************************************************************
+/* **************************************************************************
  * Task local data management
  *
  * Allows storing boxes with arbitrary types inside, to be accessed anywhere