| Age | Commit message (Collapse) | Author | Lines |
|---|
|
The book was located under 'src/doc/trpl' because originally, it was
going to be hosted under that URL. Late in the game, before 1.0, we
decided that /book was a better one, so we changed the output, but
not the input. This causes confusion for no good reason. So we'll change
the source directory to look like the output directory, like for every
other thing in src/doc.
|
|
I read this section a few times before even having a guess what
was meant, then consulted IRC for confirmation. It may be that I
was thick-headed, but I think this is a useful addition.
|
|
I read this section a few times before even having a guess what
was meant, then consulted IRC for confirmation. It may be that I
was thick-headed, but I think this is a useful addition.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
I also included some smaller trait-related changes.
Fixes #26991.
r? @shepmaster
r? @steveklabnik
|
|
Squashed at reviewer's request:
Add heading at the end of the introductory material
Spice up introductory paragraphs a bit
Use quotes instead of <code> for phrase
Remove "other" in "other restrictions" (it's not obvious that any other
restrictions have been mentioned)
"Default methods" is a second-level heading, but is not a subsection of
"Where clause"
Reword "Default methods" introduction: it's not the "last feature" on
this page
|
|
|
|
This includes a new example with Rectangle, instead of reusing HasArea,
because fn area would require the Mul trait, and the added complexity of
that would be better left for the Operators and Overloading chapter.
Squashed at reviewer's request: Move teaser for trait bounds to bottom
|
|
Instead of bar/baz, use valid/invalid as default methods. This
illustrates why you might want default methods, and shows that you can
call other trait methods from a default method.
|
|
The font can make this hard to read, and we don't even strictly need
the annotation, so let's just remove it
Fixes #26287
|
|
I saw a variation of this definition in [an article](http://pcwalton.github.io/blog/2012/08/08/a-gentle-introduction-to-traits-in-rust) by @pcwalton.
|
|
|
|
|
|
|
|
|
|
"workd" corrected to "world"
|
|
|
|
This adds strictly more information to the source files and reduces the need for customized tooling to render the book. (While this should not change the output of _rustbook_, it is very useful when rendering the sources with external tools like Pandoc.)
This only adds the language marker to "first level" code blocks (and not to code blocks in comments inside of code examples).
r? @steveklabnik
|
|
This adds strictly more information to the source files and reduces the
need for customized tooling to render the book.
(While this should not change the output of _rustbook_, it is very
useful when rendering the sources with external tools like Pandoc.)
|
|
The byte string literal syntax `b"whatever"` is more idiomatic than
`"whatever".as_bytes()`.
|
|
The source code uses `"whatever".as_bytes()`, not `b"whatever"`.
|
|
The Traits chapter uses "adding methods to `int`" as an example of "something bad", but there is no such thing as `int` anymore, right? So I changed it to `i32`.
|
|
|
|
|
|
This API was exercised in a few tests and mirrors the `from_str_radix`
functionality of the integer types.
|
|
Let's talk about generics first, since we use traits to bound them
in funtions.
Partially addresses #24325
Fixes #24271
|
|
|
|
traits.md said:
If we add a `use` line right above `main` and make the right things public,
everything is fine:
However, the use line was actually placed at the top of the file instead. Move
the use line to right above main. That also makes the example more evocative
of cases where the module is defined in a separate file.
|
|
Fixes #23688
|
|
r? @steveklabnik
|
|
|
|
|
|
|
|
Closes #21859.
|
|
Largely taken from @huonw's
http://huonw.github.io/blog/2015/01/peeking-inside-trait-objects/
Fixes #21707
|
|
Fix all usage of int/uint/i/u in the book.
|
|
Fixes #17224
|
|
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.
|
|
|
