rust/src/doc
Patrick Walton 5b85c8cbe7 librustc: Forbid pattern bindings after @s, for memory safety.
This is an alternative to upgrading the way rvalues are handled in the
borrow check. Making rvalues handled more like lvalues in the borrow
check caused numerous problems related to double mutable borrows and
rvalue scopes. Rather than come up with more borrow check rules to try
to solve these problems, I decided to just forbid pattern bindings after
`@`. This affected fewer than 10 lines of code in the compiler and
libraries.

This breaks code like:

    match x {
        y @ z => { ... }
    }

    match a {
        b @ Some(c) => { ... }
    }

Change this code to use nested `match` or `let` expressions. For
example:

    match x {
        y => {
            let z = y;
            ...
        }
    }

    match a {
        Some(c) => {
            let b = Some(c);
            ...
        }
    }

Closes #14587.

[breaking-change]
2014-08-01 08:45:22 -07:00
..
complement-bugreport.md Update repo location 2014-06-16 18:16:36 -07:00
complement-design-faq.md Update repo location 2014-06-16 18:16:36 -07:00
complement-lang-faq.md Add note about production deployments. 2014-07-31 11:50:24 -07:00
complement-project-faq.md
favicon.inc webfonts: serve Source Code Pro locally 2014-07-08 20:31:26 +02:00
footer.inc rustdoc: Submit examples to play.rust-lang.org 2014-06-06 20:00:16 -07:00
full-toc.inc doc: add webfonts and tweak the styles accordingly 2014-04-19 21:25:35 +09:00
guide-container.md docs: Fix typo in container guide. 2014-07-27 10:14:44 +02:00
guide-ffi.md doc/guide-ffi: A few minor typo/language fixes 2014-07-04 20:09:28 +02:00
guide-lifetimes.md Remove incorrect example 2014-07-31 11:50:24 -07:00
guide-macros.md looks like a cut-n-paste error in unused code 2014-06-27 22:11:11 -07:00
guide-pointers.md Fix heading levels in pointer guide 2014-07-31 07:30:52 -07:00
guide-runtime.md Rename all raw pointers as necessary 2014-06-28 11:53:58 -07:00
guide-strings.md Include Strings guide with the others. 2014-07-18 10:48:24 -04:00
guide-tasks.md std: Rename the ToStr trait to ToString, and to_str to to_string. 2014-07-08 13:01:43 -07:00
guide-testing.md librustc: Remove the fallback to int from typechecking. 2014-06-24 17:18:48 -07:00
guide-unsafe.md librustc: Remove the fallback to int for integers and f64 for 2014-06-29 11:47:58 -07:00
guide.md New Guide: crates and modules 2014-07-29 12:50:25 -04:00
index.md adding discuss.rust-lang to community 2014-07-29 15:44:08 -07:00
intro.md Update disclaimer to improve clarity and intent 2014-07-29 15:43:02 -07:00
not_found.md Change static.rust-lang.org to doc.rust-lang.org 2014-05-21 19:55:39 -07:00
po4a.conf Remove obsolete Japanese translation for a while. 2014-07-25 06:51:32 +09:00
README.md Update to 0.11.0 2014-06-27 12:50:16 -07:00
rust.css webfonts: serve Source Code Pro locally 2014-07-08 20:31:26 +02:00
rust.md librustc: Forbid pattern bindings after @s, for memory safety. 2014-08-01 08:45:22 -07:00
rustdoc.md Fix example in docs on documentation 2014-07-02 10:53:30 +02:00
tutorial.md fix variable name in tutorial 2014-07-31 07:30:14 -07:00
version_info.html.template Update repo location 2014-06-16 18:16:36 -07:00

Dependencies

Pandoc, a universal document converter, is required to generate docs as HTML from Rust's source code.

po4a is required for generating translated docs from the master (English) docs.

GNU gettext is required for managing the translation data.

Building

To generate all the docs, just run make docs from the root of the repository. This will convert the distributed Markdown docs to HTML and generate HTML doc for the 'std' and 'extra' libraries.

To generate HTML documentation from one source file/crate, do something like:

rustdoc --output-dir html-doc/ --output-format html ../src/libstd/path.rs

(This, of course, requires a working build of the rustdoc tool.)

Additional notes

To generate an HTML version of a doc from Markdown manually, you can do something like:

pandoc --from=markdown --to=html5 --number-sections -o rust.html rust.md

(rust.md being the Rust Reference Manual.)

The syntax for pandoc flavored markdown can be found at: http://johnmacfarlane.net/pandoc/README.html#pandocs-markdown

A nice quick reference (for non-pandoc markdown) is at: http://kramdown.rubyforge.org/quickref.html

Notes for translators

Notice: The procedure described below is a work in progress. We are working on translation system but the procedure contains some manual operations for now.

To start the translation for a new language, see po4a.conf at first.

To generate .pot and .po files, do something like:

po4a --copyright-holder="The Rust Project Developers" \
    --package-name="Rust" \
    --package-version="0.11.0" \
    -M UTF-8 -L UTF-8 \
    src/doc/po4a.conf

(the version number must be changed if it is not 0.11.0 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 manual linked from http://www.gnu.org/software/gettext/ . We use UTF-8 as the file encoding of .po files.

When you want to make a commit, do the command below before staging your change:

for f in src/doc/po/**/*.po; do
    msgattrib --translated $f -o $f.strip
    if [ -e $f.strip ]; then
       mv $f.strip $f
    else
       rm $f
    fi
done

This removes untranslated entries from .po files to save disk space.