| Age | Commit message (Collapse) | Author | Lines |
|---|
|
|
|
more more more
|
|
A brief introduction to each type, with pointers to the primitive pages
for more info.
|
|
keeping on with the edits
|
|
Fill out blank section headers. Copy edit the entire first section.
|
|
Now that the new TOC has landed, I've started doing an editing pass to get the old content into the right shape. I felt this introduction was significant enough to send as its own PR, though, as it's the introduction.
It's possible that we may just want to replace 'the intro' with this directly, but this PR doesn't do that.
|
|
#24004
Something like this?
|
|
|
|
Fill out blank section headers. Copy edit the entire first section.
|
|
|
|
|
|
This also puts slice patterns in nightly docs, where they belong.
|
|
|
|
I decided to break if-let out, as it's too complex for this part, but moving
if that late seems silly too.
|
|
This doesn't actually display correctly
|
|
As I go through this, I'm finding some ways that I want to tweak the order.
|
|
This commit series starts out with more official test harness support for rustdoc tests, and then each commit afterwards adds a test (where appropriate). Each commit should also test and finish independently of all others (they're all pretty separable).
I've uploaded a [copy of the documentation](http://people.mozilla.org/~acrichton/doc/std/) generated after all these commits were applied, and a double check on issues being closed would be greatly appreciated! I'll also browse the docs a bit and make sure nothing regressed too horribly.
|
|
|
|
|
|
A brief introduction to each type, with pointers to the primitive pages
for more info.
|
|
|
|
|
|
Can anyone take a look? Very trivial.
|
|
|
|
|
|
Right now rustdoc replaces the string ".md)" with ".html)" to fix links between
markdown files, so use a different syntax that doesn't get caught in the
crossfire.
Closes #22900
|
|
|
|
|
|
People use programming language *implementations* like Ruby MRI, CPython, and SpiderMonkey for executing programs.
|
|
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 #24060.
|
|
Fixes #24030
Of the four code samples with modules in TRPL:
- 2 use `mod test`
- 2 use `mod tests`
We should be consistent here, but which is right? The stdlib is split:
$ grep -r 'mod tests {' src/lib* | wc -l
63
$ grep -r 'mod test {' src/lib* | wc -l
58
Subjectively, I like the plural, but both the language reference and the
style guide recommend the singular. So we'll go with that here, for now.
r? @steveklabnik
|
|
People use programming language *implementations* like Ruby MRI, CPython, and SpiderMonkey for executing programs.
|
|
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.
|
|
|
|
Correct mistyped comma, and slightly improve sentence.
r? @steveklabnik
|
|
Correct mistyped comma, and slightly improve sentence.
|
|
|
|
Ran across this one while learning from the Book.
|
|
I ran across a comma splice.
I didn't set the "note:" off inside parenthesis. I looked around in other places and saw it both ways, but without surrounding parenthesis seemed to be the more common convention followed elsewhere in the docs. Let me know if you have an overriding preference about that and I'll change it.
r? @steveklabnik
|
|
This syncs the _Crates and Modules_ chapter of the book with current output:
* the runs are supposed to be in the project’s directory,
* `rustc` has slightly different error messages (and things like macro line:col numbers),
* Cargo now compiles things into `target/debug`.
|
|
|
|
|
|
Default is now beta, add nightly in the unstable section
|
|
Fixes #24030
Of the four code samples with modules in TRPL:
- 2 use `mod test`
- 2 use `mod tests`
We should be consistent here, but which is right? The stdlib is split:
$ grep -r 'mod tests {' src/lib* | wc -l
63
$ grep -r 'mod test {' src/lib* | wc -l
58
Subjectively, I like the plural, but both the language reference and the
style guide recommend the singular. So we'll go with that here, for now.
|
|
|
|
Default is now beta, add nightly in the unstable section
|
|
Also: the std_misc feature flag is removed; it's not needed in Beta.
Hat tip to @tshepang in #23871
Fixes #24023
|
|
|
|
|
