---

yaml
---
r: 96111
b: refs/heads/dist-snap
c: 5748699
h: refs/heads/master
i:
  96109: 07418a6
  96107: 4700fae
  96103: 4c098a7
  96095: 16a863d
v: v3

Author: z0w0

[refs]

@@ -6,7 +6,7 @@ refs/heads/try: c274a6888410ce3e357e014568b43310ed787d36
 refs/tags/release-0.1: 1f5c5126e96c79d22cb7862f75304136e204f105
 refs/heads/ndm: f3868061cd7988080c30d6d5bf352a5a5fe2460b
 refs/heads/try2: 147ecfdd8221e4a4d4e090486829a06da1e0ca3c
-refs/heads/dist-snap: b0e1318164f6b496c513a93fd745faabfd225ef5
+refs/heads/dist-snap: 57486994d56e57044a37144fa6f741a946ff295a
 refs/tags/release-0.2: c870d2dffb391e14efb05aa27898f1f6333a9596
 refs/tags/release-0.3: b5f0d0f648d9a6153664837026ba1be43d3e2503
 refs/heads/try3: 9387340aab40a73e8424c48fd42f0c521a4875c0

branches/dist-snap/.gitignore

@@ -89,4 +89,3 @@ config.stamp
 src/etc/dl
 .settings/
 build/
-i686-pc-mingw32/

branches/dist-snap/doc/favicon.inc

@@ -4,9 +4,4 @@
     display: block;
     padding-left: 2em;
   }
-  #influences blockquote p:last-child {
-    display: block;
-    line-height: 1.428571429;
-    color: #999999;
-  }
-</style>
+</style>

branches/dist-snap/doc/manual.inc

@@ -529,7 +529,7 @@ msgid ""
 "The basic example below illustrates this.\n"
 "~~~\n"
 "# fn make_a_sandwich() {};\n"
-"fn fib(n: u64) -> u64 {\n"
+"fn fib(n: uint) -> uint {\n"
 "    // lengthy computation returning an uint\n"
 "    12586269025\n"
 "}\n"

branches/dist-snap/doc/po/ja/tutorial-tasks.md.po

@@ -529,7 +529,7 @@ msgid ""
 "The basic example below illustrates this.\n"
 "~~~\n"
 "# fn make_a_sandwich() {};\n"
-"fn fib(n: u64) -> u64 {\n"
+"fn fib(n: uint) -> uint {\n"
 "    // lengthy computation returning an uint\n"
 "    12586269025\n"
 "}\n"

branches/dist-snap/doc/po/tutorial-tasks.md.pot

@@ -2,7 +2,7 @@
  * Copyright 2013 The Rust Project Developers. See the COPYRIGHT
  * file at the top-level directory of this distribution and at
  * http://rust-lang.org/COPYRIGHT.
- * With elements taken from Bootstrap v3.0.2 (MIT licensed).
+ * With elements taken from Bootstrap v3.0.0 (Apache v2.0 licensed).
  *
  * Licensed under the Apache License, Version 2.0 <LICENSE-APACHE or
  * http://www.apache.org/licenses/LICENSE-2.0> or the MIT license
@@ -93,7 +93,6 @@ p {
 a {
 	text-decoration: none;
 	color: #428BCA;
-	background: transparent;
 }
 a:hover, a:focus {
 	color: #2A6496;
@@ -115,7 +114,7 @@ h5 a:link, h5 a:visited {color: black;}
 /* Code
    ========================================================================== */
 pre, code {
-	font-family: Menlo, Monaco, Consolas, "Courier New", monospace;
+	font-family: Monaco, Menlo, Consolas, "Courier New", monospace;
 	border-radius: 4px;
 }
 pre {
@@ -142,7 +141,7 @@ pre code {
 	color: inherit;
 	white-space: pre-wrap;
 	background-color: transparent;
-	border-radius: 0;
+	border: 0;
 }
 
 /* Code highlighting */
@@ -159,7 +158,7 @@ pre code {
 .cm-s-default span.cm-string {color: #a11;}
 .cm-s-default span.cm-string-2 {color: #f50;}
 .cm-s-default span.cm-meta {color: #555;}
-/*.cm-s-default span.cm-error {color: #f00;}*/
+.cm-s-default span.cm-error {color: #f00;}
 .cm-s-default span.cm-qualifier {color: #555;}
 .cm-s-default span.cm-builtin {color: #30a;}
 .cm-s-default span.cm-bracket {color: #cc7;}
@@ -188,7 +187,7 @@ pre code {
 }
 #versioninfo a.hash {
 	color: gray;
-	font-size: 70%;
+	font-size: 60%;
 }
 
 blockquote {
@@ -304,4 +303,4 @@ hr {
 	table td, table th {
 		background-color: #fff !important;
 	}
-}
+}

branches/dist-snap/doc/rust.css

@@ -120,7 +120,7 @@ Thus, there should be no need to pass a `-L` flag to rustpkg to tell it where to
 
 # Custom build scripts
 
-A file called `pkg.rs` at the root level in a package directory is called a *package script*.
+A file called `pkg.rs` at the root level in a workspace is called a *package script*.
 If a package script exists, rustpkg executes it to build the package
 rather than inferring crates as described previously.
 

branches/dist-snap/doc/rustpkg.md

@@ -303,7 +303,7 @@ conventions. Rust provides a way to tell the compiler which convention to use:
 #[cfg(target_os = "win32", target_arch = "x86")]
 #[link_name = "kernel32"]
 extern "stdcall" {
-    fn SetEnvironmentVariableA(n: *u8, v: *u8) -> std::libc::c_int;
+    fn SetEnvironmentVariableA(n: *u8, v: *u8) -> int;
 }
 ~~~~
 

branches/dist-snap/doc/tutorial-ffi.md

@@ -210,10 +210,10 @@ solves the problem.
 
 # Macro argument pattern matching
 
-## Motivation
-
 Now consider code like the following:
 
+## Motivation
+
 ~~~~
 # enum t1 { good_1(t2, uint), bad_1 };
 # pub struct t2 { body: t3 }

branches/dist-snap/doc/tutorial-macros.md

@@ -27,6 +27,7 @@ $ rustc main.rs
 main.rs:1:0: 1:17 error: can't find crate for `hello`
 main.rs:1 extern mod hello;
           ^~~~~~~~~~~~~~~~~
+
 ~~~~
 
 This makes sense, as we haven't gotten it from anywhere yet!  Luckily for us,
@@ -215,7 +216,7 @@ a function that can be sensibly tested:
 #[license = "MIT"];
 
 pub fn is_even(i: uint) -> bool {
-    i % 2 == 0
+	i % 2 == 0
 }
 ~~~
 
@@ -229,9 +230,9 @@ use hello::is_even;
 
 #[test]
 fn test_is_even() {
-    assert!(is_even(0));
-    assert!(!is_even(1));
-    assert!(is_even(2));
+   assert!(is_even(0));
+   assert!(!is_even(1));
+   assert!(is_even(2));	
 }
 ~~~
 

branches/dist-snap/doc/tutorial-rustpkg.md

@@ -104,8 +104,8 @@ an environment that it carries across tasks.
 let child_task_number = generate_task_number();
 
 do spawn {
-    // Capture it in the remote task
-    println!("I am child number {}", child_task_number);
+   // Capture it in the remote task
+   println!("I am child number {}", child_task_number);
 }
 ~~~
 
@@ -273,7 +273,7 @@ later.
 The basic example below illustrates this.
 ~~~
 # fn make_a_sandwich() {};
-fn fib(n: u64) -> u64 {
+fn fib(n: uint) -> uint {
     // lengthy computation returning an uint
     12586269025
 }

branches/dist-snap/doc/tutorial-tasks.md

@@ -804,7 +804,7 @@ confusing numbers that correspond to different units.
 We've already seen several function definitions. Like all other static
 declarations, such as `type`, functions can be declared both at the
 top level and inside other functions (or in modules, which we'll come
-back to [later](#crates-and-the-module-system)). The `fn` keyword introduces a
+back to [later](#modules-and-crates)). The `fn` keyword introduces a
 function. A function has an argument list, which is a parenthesized
 list of `expr: type` pairs separated by commas. An arrow `->`
 separates the argument list and the function's return type.
@@ -2550,21 +2550,18 @@ fn main() {
 ~~~~
 
 And here an example with multiple files:
-
 ~~~{.ignore}
 // a.rs - crate root
 use b::foo;
 mod b;
 fn main() { foo(); }
 ~~~
-
 ~~~{.ignore}
 // b.rs
 use b::c::bar;
 pub mod c;
 pub fn foo() { bar(); }
 ~~~
-
 ~~~
 // c.rs
 pub fn bar() { println("Baz!"); }
@@ -2714,10 +2711,10 @@ extend with the `-L` switch).
 However, Rust also ships with rustpkg, a package manager that is able to automatically download and build
 libraries if you use it for building your crate. How it works is explained [here][rustpkg],
 but for this tutorial it's only important to know that you can optionally annotate an
-`extern mod` statement with a package id that rustpkg can use to identify it:
+`extern mod` statement with an package id that rustpkg can use to identify it:
 
 ~~~ {.ignore}
-extern mod rust = "github.com/mozilla/rust"; // pretend Rust is a simple library
+extern mod rust = "github.com/mozilla/rust"; // pretend Rust is an simple library
 ~~~
 
 [rustpkg]: rustpkg.html
@@ -2733,7 +2730,7 @@ the link name and the version. It also hashes the filename and the symbols in a
 based on the link metadata, allowing you to use two different versions of the same library in a crate
 without conflict.
 
-Therefore, if you plan to compile your crate as a library, you should annotate it with that information:
+Therefor, if you plan to compile your crate as a library, you should annotate it with that information:
 
 ~~~~
 // lib.rs
@@ -2749,8 +2746,8 @@ Therefore, if you plan to compile your crate as a library, you should annotate i
 You can also in turn require in a `extern mod` statement that certain link metadata items match some criteria.
 For that, Rust currently parses a comma-separated list of name/value pairs that appear after
 it, and ensures that they match the attributes provided in the `link` attribute of a crate file.
-This enables you to, e.g., pick a crate based on its version number, or link a library under a
-different name. For example, these two `mod` statements would both accept and select the crate define above:
+This enables you to, eg, pick a a crate based on it's version number, or to link an library under an
+different name. For example, this two mod statements would both accept and select the crate define above:
 
 ~~~~ {.xfail-test}
 extern mod farm(vers = "2.5");
@@ -2839,15 +2836,15 @@ This allows you to use common types and functions like `Option<T>` or `println`
 without needing to import them. And if you need something from `std` that's not in the prelude,
 you just have to import it with an `use` statement.
 
-For example, it re-exports `println` which is defined in `std::io::stdio::println`:
+For example, it re-exports `println` which is defined in `std::io::println`:
 
 ~~~
-use puts = std::io::stdio::println;
+use puts = std::rt::io::stdio::println;
 
 fn main() {
     println("println is imported per default.");
-    puts("Doesn't hinder you from importing it under a different name yourself.");
-    ::std::io::stdio::println("Or from not using the automatic import.");
+    puts("Doesn't hinder you from importing it under an different name yourself.");
+    ::std::rt::io::stdio::println("Or from not using the automatic import.");
 }
 ~~~