| Age | Commit message (Collapse) | Author | Lines |
|---|
|
Fixes #20993
|
|
Also, update description of macro invocation syntax:
after https://github.com/rust-lang/rust/pull/20563 there is
a number of additional limitations on macro syntax.
|
|
|
|
|
|
uint was recently deprecated, so in following the use of i32 at first,
replace all references to uint with u32.
Also change literals from e.g. 100u to 100, so that they are no longer
usize.
|
|
Fixing integer usage in ownership doc
Reviewed-by: steveklabnik
|
|
replace deprecated uint references with u32 in trpl/looping.md
Reviewed-by: Gankro
|
|
TRPL: `cargo build` doesn't run executables
Reviewed-by: alexcrichton
|
|
Switching out range(0,10) example to 0..10. Tests fine
Reviewed-by: brson
|
|
Hepburn romanization of さようなら
Reviewed-by: huonw
|
|
Cosmetic updates to TRPL text
Reviewed-by: steveklabnik
|
|
Error Guide: Add Line Break to Robert Burns Quote
Reviewed-by: steveklabnik
|
|
Closure documentation: Fix boxed closure left-over
Reviewed-by: steveklabnik
|
|
`int` doesn't exist anymore. Usage of its equivalent `isize` is
discouraged since its size is platform-dependent. `i32` is used instead
in the examples. Also, integer suffixes aren't needed in the examples
anymore so we can just write `5` instead of `5i`.
|
|
Replaced uint references with u32 to prevent compiler warnings.
|
|
|
|
|
|
|
|
* Make messages match rustc's error messages
* Use correct function name in example
* Rewording to match previously presented material
|
|
|
|
Docs: Should be `assert_eq!` not `assert_eq`
Reviewed-by: sfackler
|
|
Fix typo in documentation.
Reviewed-by: sfackler
|
|
Fix a couple wording issues in TRPL book
Reviewed-by: Gankro
|
|
Fixes typo
Reviewed-by: alexcrichton
|
|
Remove extra dangling period
Reviewed-by: alexcrichton
|
|
Update Conclusion of The Rust Programming Language
Reviewed-by: steveklabnik
|
|
|
|
|
|
Here's my PR for the changes discussed in #19823. I decided to leave `_these_` types of italics the way there were because it differentiates the use of italics for emphasis from `*key term*` italics. Otherwise, bolded terms have been changed to italics, and single and double quotes have been changed appropriately, depending on their context (my judgement may not be the best, though).
r? @steveklabnik (congratulations on #19897 being finalized and merged, by the way!)
|
|
|
|
a type parameter for closures.
|
|
|
|
|
|
Signed-off-by: Raul Gutierrez S <rgs@itevenworks.net>
|
|
This replaces a obsolete conclusion (based on the original, basic Guide) with
links to further documentation sources.
|
|
This commit is an attempt to standardize the use of punctuation and
formatting in "The Rust Programming Language" as discussed in #19823.
- Convert bold text to italicized textcwhen referring to terminology.
- Convert single-quoted text to italicized or double-quoted text,
depending on context.
- Use double quotes only in the case of scare quotes or quotations.
|
|
|
|
This pulls all of our long-form documentation into a single document,
nicknamed "the book" and formally titled "The Rust Programming
Language."
A few things motivated this change:
* People knew of The Guide, but not the individual Guides. This merges
them together, helping discoverability.
* You can get all of Rust's longform documentation in one place, which
is nice.
* We now have rustbook in-tree, which can generate this kind of
documentation. While its style is basic, the general idea is much
better: a table of contents on the left-hand side.
* Rather than a almost 10,000-line guide.md, there are now smaller files
per section.
|
