---

yaml
---
r: 110091
b: refs/heads/auto
c: a5681d2
h: refs/heads/master
i:
  110089: 3c05a81
  110087: 0964aea
v: v3

Author: alexcrichton

[refs]

@@ -13,7 +13,7 @@ refs/heads/try3: 9387340aab40a73e8424c48fd42f0c521a4875c0
 refs/tags/release-0.3.1: 495bae036dfe5ec6ceafd3312b4dca48741e845b
 refs/tags/release-0.4: e828ea2080499553b97dfe33b3f4d472b4562ad7
 refs/tags/release-0.5: 7e3bcfbf21278251ee936ad53e92e9b719702d73
-refs/heads/auto: 6f1c06d6a1b97fcd80d85c38bb33f8350c750401
+refs/heads/auto: a5681d25906fd07eee00dd430a1053ff722da26a
 refs/heads/servo: af82457af293e2a842ba6b7759b70288da276167
 refs/tags/release-0.6: b4ebcfa1812664df5e142f0134a5faea3918544c
 refs/tags/0.1: b19db808c2793fe2976759b85a355c3ad8c8b336

branches/auto/README.md

@@ -32,9 +32,9 @@ documentation.
 
     To build from the [tarball] do:
 
-        $ curl -O http://static.rust-lang.org/dist/rust-0.9.tar.gz
-        $ tar -xzf rust-0.9.tar.gz
-        $ cd rust-0.9
+        $ curl -O http://static.rust-lang.org/dist/rust-0.10.tar.gz
+        $ tar -xzf rust-0.10.tar.gz
+        $ cd rust-0.10
 
     Or to build from the [repo] do:
 
@@ -59,8 +59,8 @@ documentation.
 4. Enjoy!
 
 [repo]: https://github.com/mozilla/rust
-[tarball]: http://static.rust-lang.org/dist/rust-0.9.tar.gz
-[tutorial]: http://static.rust-lang.org/doc/0.9/tutorial.html
+[tarball]: http://static.rust-lang.org/dist/rust-0.10.tar.gz
+[tutorial]: http://static.rust-lang.org/doc/0.10/tutorial.html
 
 ## Notes
 

branches/auto/RELEASES.txt

@@ -6,10 +6,7 @@ Version 0.10 (April 2014)
   * Language
     * A new RFC process is now in place for modifying the language.
     * Patterns with `@`-pointers have been removed from the language.
-    * Patterns with unique vectors (`~[T]`) have been removed from the
-      language.
-    * Patterns with unique strings (`~str`) have been removed from the
-      language.
+    * Patterns with unique vectors have been removed from the language.
     * `@str` has been removed from the language.
     * `@[T]` has been removed from the language.
     * `@self` has been removed from the language.
@@ -28,10 +25,9 @@ Version 0.10 (April 2014)
       * Camel Case types
       * Uppercase variables
       * Publicly visible private types
-      * `#[deriving]` with raw pointers
     * Unsafe functions can no longer be coerced to closures.
     * Various obscure macros such as `log_syntax!` are now behind feature gates.
-    * The `#[simd]` attribute is now behind a feature gate.
+    * The #[simd] attribute is now behind a feature gate.
     * Visibility is no longer allowed on `extern crate` statements, and
       unnecessary visibility (`priv`) is no longer allowed on `use` statements.
     * Trailing commas are now allowed in argument lists and tuple patterns.
@@ -43,7 +39,7 @@ Version 0.10 (April 2014)
     * The `Share` trait has been added for types that can be shared among
       threads.
     * Labels in macros are now hygienic.
-    * Expression/statement macro invocations can be delimited with `{}` now.
+    * Expresson/statement macro invocations can be delimited with `{}` now.
     * Treatment of types allowed in `static mut` locations has been tweaked.
     * The `*` and `.` operators are now overloadable through the `Deref` and
       `DerefMut` traits.
@@ -149,20 +145,16 @@ Version 0.10 (April 2014)
     * Output flags have been centralized into one `--emit` flag.
     * Crate type flags have been centralized into one `--crate-type` flag.
     * Codegen flags have been consolidated behind a `-C` flag.
+    * `rustdoc` now implements syntax highlighting and rendering markdown files.
+    * `rustdoc --test` now tests all code blocks by default.
+    * `rustdoc` now shows documented macros.
+    * `rustdoc` inlines documentation for reexported types.
+    * `rustdoc` search works across crates now.
     * Linking against outdated crates now has improved error messages.
     * Error messages with lifetimes will often suggest how to annotate the
       function to fix the error.
     * Many more types are documented in the standard library, and new guides
       were written.
-    * Many `rustdoc` improvements:
-      * code blocks are syntax highlighted.
-      * render standalone markdown files.
-      * the --test flag tests all code blocks by default.
-      * exported macros are displayed.
-      * reexported types have their documentation inlined at the location of the
-        first reexport.
-      * search works across crates that have been rendered to the same output
-        directory.
 
 Version 0.9 (January 2014)
 --------------------------

branches/auto/man/rustc.1

@@ -1,4 +1,4 @@
-.TH RUSTC "1" "March 2014" "rustc 0.10-pre" "User Commands"
+.TH RUSTC "1" "March 2014" "rustc 0.10" "User Commands"
 .SH NAME
 rustc \- rust compiler
 .SH SYNOPSIS

branches/auto/man/rustdoc.1

@@ -1,4 +1,4 @@
-.TH RUSTDOC "1" "March 2014" "rustdoc 0.10-pre" "User Commands"
+.TH RUSTDOC "1" "March 2014" "rustdoc 0.10" "User Commands"
 .SH NAME
 rustdoc \- generate documentation from Rust source code
 .SH SYNOPSIS

branches/auto/mk/main.mk

@@ -14,7 +14,7 @@
 
 # The version number
 CFG_RELEASE_NUM=0.10
-CFG_RELEASE_LABEL=-pre
+CFG_RELEASE_LABEL=
 
 ifndef CFG_ENABLE_NIGHTLY
 # This is the normal version string

branches/auto/src/compiletest/common.rs

@@ -21,87 +21,87 @@ pub enum mode {
 #[deriving(Clone)]
 pub struct config {
     // The library paths required for running the compiler
-    pub compile_lib_path: ~str,
+    compile_lib_path: ~str,
 
     // The library paths required for running compiled programs
-    pub run_lib_path: ~str,
+    run_lib_path: ~str,
 
     // The rustc executable
-    pub rustc_path: Path,
+    rustc_path: Path,
 
     // The clang executable
-    pub clang_path: Option<Path>,
+    clang_path: Option<Path>,
 
     // The llvm binaries path
-    pub llvm_bin_path: Option<Path>,
+    llvm_bin_path: Option<Path>,
 
     // The directory containing the tests to run
-    pub src_base: Path,
+    src_base: Path,
 
     // The directory where programs should be built
-    pub build_base: Path,
+    build_base: Path,
 
     // Directory for auxiliary libraries
-    pub aux_base: Path,
+    aux_base: Path,
 
     // The name of the stage being built (stage1, etc)
-    pub stage_id: ~str,
+    stage_id: ~str,
 
     // The test mode, compile-fail, run-fail, run-pass
-    pub mode: mode,
+    mode: mode,
 
     // Run ignored tests
-    pub run_ignored: bool,
+    run_ignored: bool,
 
     // Only run tests that match this filter
-    pub filter: Option<~str>,
+    filter: Option<~str>,
 
     // Write out a parseable log of tests that were run
-    pub logfile: Option<Path>,
+    logfile: Option<Path>,
 
     // Write out a json file containing any metrics of the run
-    pub save_metrics: Option<Path>,
+    save_metrics: Option<Path>,
 
     // Write and ratchet a metrics file
-    pub ratchet_metrics: Option<Path>,
+    ratchet_metrics: Option<Path>,
 
     // Percent change in metrics to consider noise
-    pub ratchet_noise_percent: Option<f64>,
+    ratchet_noise_percent: Option<f64>,
 
-    // "Shard" of the testsuite to pub run: this has the form of
+    // "Shard" of the testsuite to run: this has the form of
     // two numbers (a,b), and causes only those tests with
     // positional order equal to a mod b to run.
-    pub test_shard: Option<(uint,uint)>,
+    test_shard: Option<(uint,uint)>,
 
     // A command line to prefix program execution with,
     // for running under valgrind
-    pub runtool: Option<~str>,
+    runtool: Option<~str>,
 
     // Flags to pass to the compiler when building for the host
-    pub host_rustcflags: Option<~str>,
+    host_rustcflags: Option<~str>,
 
     // Flags to pass to the compiler when building for the target
-    pub target_rustcflags: Option<~str>,
+    target_rustcflags: Option<~str>,
 
     // Run tests using the JIT
-    pub jit: bool,
+    jit: bool,
 
     // Target system to be tested
-    pub target: ~str,
+    target: ~str,
 
     // Host triple for the compiler being invoked
-    pub host: ~str,
+    host: ~str,
 
     // Extra parameter to run adb on arm-linux-androideabi
-    pub adb_path: ~str,
+    adb_path: ~str,
 
     // Extra parameter to run test sute on arm-linux-androideabi
-    pub adb_test_dir: ~str,
+    adb_test_dir: ~str,
 
     // status whether android device available or not
-    pub adb_device_status: bool,
+    adb_device_status: bool,
 
     // Explain what's going on
-    pub verbose: bool
+    verbose: bool
 
 }

branches/auto/src/compiletest/errors.rs

@@ -10,11 +10,7 @@
 
 use std::io::{BufferedReader, File};
 
-pub struct ExpectedError {
-    pub line: uint,
-    pub kind: ~str,
-    pub msg: ~str,
-}
+pub struct ExpectedError { line: uint, kind: ~str, msg: ~str }
 
 // Load any test directives embedded in the file
 pub fn load_errors(testfile: &Path) -> Vec<ExpectedError> {

branches/auto/src/compiletest/header.rs

@@ -14,26 +14,26 @@ use util;
 
 pub struct TestProps {
     // Lines that should be expected, in order, on standard out
-    pub error_patterns: Vec<~str> ,
+    error_patterns: Vec<~str> ,
     // Extra flags to pass to the compiler
-    pub compile_flags: Option<~str>,
+    compile_flags: Option<~str>,
     // If present, the name of a file that this test should match when
     // pretty-printed
-    pub pp_exact: Option<Path>,
+    pp_exact: Option<Path>,
     // Modules from aux directory that should be compiled
-    pub aux_builds: Vec<~str> ,
+    aux_builds: Vec<~str> ,
     // Environment settings to use during execution
-    pub exec_env: Vec<(~str,~str)> ,
+    exec_env: Vec<(~str,~str)> ,
     // Commands to be given to the debugger, when testing debug info
-    pub debugger_cmds: Vec<~str> ,
+    debugger_cmds: Vec<~str> ,
     // Lines to check if they appear in the expected debugger output
-    pub check_lines: Vec<~str> ,
+    check_lines: Vec<~str> ,
     // Flag to force a crate to be built with the host architecture
-    pub force_host: bool,
+    force_host: bool,
     // Check stdout for error-pattern output as well as stderr
-    pub check_stdout: bool,
+    check_stdout: bool,
     // Don't force a --crate-type=dylib flag on the command line
-    pub no_prefer_dynamic: bool,
+    no_prefer_dynamic: bool,
 }
 
 // Load any test directives embedded in the file

branches/auto/src/compiletest/procsrv.rs

@@ -57,7 +57,7 @@ fn target_env(lib_path: &str, prog: &str) -> Vec<(~str,~str)> {
     return env;
 }
 
-pub struct Result {pub status: ProcessExit, pub out: ~str, pub err: ~str}
+pub struct Result {status: ProcessExit, out: ~str, err: ~str}
 
 pub fn run(lib_path: &str,
            prog: &str,

branches/auto/src/doc/README.md

@@ -53,12 +53,12 @@ To generate .pot and .po files, do something like:
 ~~~~
 po4a --copyright-holder="The Rust Project Developers" \
     --package-name="Rust" \
-    --package-version="0.10-pre" \
+    --package-version="0.10" \
     -M UTF-8 -L UTF-8 \
     src/doc/po4a.conf
 ~~~~
 
-(the version number must be changed if it is not 0.10-pre now.)
+(the version number must be changed if it is not 0.10 now.)
 
 Now you can translate documents with .po files, commonly used with gettext. If
 you are not familiar with gettext-based translation, please read the online

branches/auto/src/doc/complement-lang-faq.md

@@ -31,10 +31,10 @@ You may also be interested in browsing [GitHub's Rust][github-rust] page.
 
 ## Does it run on Windows?
 
-Yes. All development happens in lock-step on all 3 target platforms. Using MinGW, not Cygwin. Note that the windows implementation currently has some limitations: in particular 64-bit build is [not fully supported yet][win64], and all executables created by rustc [depends on libgcc DLL at runtime][libgcc].
+Yes. All development happens in lock-step on all 3 target platforms. Using MinGW, not Cygwin. Note that the windows implementation currently has some limitations: in particular tasks [cannot unwind on windows][unwind], and all Rust executables [require a MinGW installation at runtime][libgcc].
 
-[win64]: https://github.com/mozilla/rust/issues/1237
-[libgcc]: https://github.com/mozilla/rust/issues/11782
+[unwind]: https://github.com/mozilla/rust/issues/908
+[libgcc]: https://github.com/mozilla/rust/issues/1603
 
 ## Is it OO? How do I do this thing I normally do in an OO language?
 

branches/auto/src/doc/guide-pointers.md

@@ -332,6 +332,8 @@ sense, they're simple: just keep whatever ownership the data already has. For
 example:
 
 ~~~rust
+use std::num::sqrt;
+
 struct Point {
     x: f32,
     y: f32,
@@ -341,7 +343,7 @@ fn compute_distance(p1: &Point, p2: &Point) -> f32 {
     let x_d = p1.x - p2.x;
     let y_d = p1.y - p2.y;
 
-    (x_d * x_d + y_d * y_d).sqrt()
+    sqrt(x_d * x_d + y_d * y_d)
 }
 
 fn main() {

branches/auto/src/doc/guide-runtime.md

@@ -216,7 +216,8 @@ into the pool of schedulers in order to spawn a new task.
 
 With two implementations of the runtime available, a choice obviously needs to
 be made to see which will be used. The compiler itself will always by-default
-link to one of these runtimes.
+link to one of these runtimes. At the time of this writing, the default runtime
+is `libgreen` but in the future this will become `libnative`.
 
 Having a default decision made in the compiler is done out of necessity and
 convenience. The compiler's decision of runtime to link to is *not* an

branches/auto/src/doc/guide-unsafe.md

@@ -200,7 +200,7 @@ use std::ptr;
 // Unique<T> has the same semantics as ~T
 pub struct Unique<T> {
     // It contains a single raw, mutable pointer to the object in question.
-    ptr: *mut T
+    priv ptr: *mut T
 }
 
 // Implement methods for creating and using the values in the box.

branches/auto/src/doc/po/ja/complement-cheatsheet.md.po

@@ -5,7 +5,7 @@
 #
 msgid ""
 msgstr ""
-"Project-Id-Version: Rust 0.10-pre\n"
+"Project-Id-Version: Rust 0.10\n"
 "POT-Creation-Date: 2014-02-03 08:13+0900\n"
 "PO-Revision-Date: 2014-01-13 12:01+0900\n"
 "Last-Translator: Automatically generated\n"

branches/auto/src/doc/po/ja/complement-lang-faq.md.po

@@ -5,7 +5,7 @@
 #
 msgid ""
 msgstr ""
-"Project-Id-Version: Rust 0.10-pre\n"
+"Project-Id-Version: Rust 0.10\n"
 "POT-Creation-Date: 2014-02-03 08:13+0900\n"
 "PO-Revision-Date: 2014-01-13 12:01+0900\n"
 "Last-Translator: Automatically generated\n"

branches/auto/src/doc/po/ja/complement-project-faq.md.po

@@ -5,7 +5,7 @@
 #
 msgid ""
 msgstr ""
-"Project-Id-Version: Rust 0.10-pre\n"
+"Project-Id-Version: Rust 0.10\n"
 "POT-Creation-Date: 2014-02-03 08:13+0900\n"
 "PO-Revision-Date: 2014-01-13 12:01+0900\n"
 "Last-Translator: Automatically generated\n"

branches/auto/src/doc/po/ja/complement-usage-faq.md.po

@@ -5,7 +5,7 @@
 #
 msgid ""
 msgstr ""
-"Project-Id-Version: Rust 0.10-pre\n"
+"Project-Id-Version: Rust 0.10\n"
 "POT-Creation-Date: 2014-02-03 08:13+0900\n"
 "PO-Revision-Date: 2014-02-03 08:13+0900\n"
 "Last-Translator: Automatically generated\n"

branches/auto/src/doc/po/ja/guide-conditions.md.po

@@ -5,7 +5,7 @@
 #
 msgid ""
 msgstr ""
-"Project-Id-Version: Rust 0.10-pre\n"
+"Project-Id-Version: Rust 0.10\n"
 "POT-Creation-Date: 2014-02-03 08:13+0900\n"
 "PO-Revision-Date: 2014-01-13 12:01+0900\n"
 "Last-Translator: Automatically generated\n"