| Age | Commit message (Collapse) | Author | Lines |
|---|
|
|
|
Rather than port each individual change to these files, for the release,
I just waited to do it all at the end, in this commit. Since individual
comits made it to master, everyone should get proper credit in the
main tree, and AUTHORS includes those whose changes are here.
|
|
|
|
An automated script was run against the `.rs` and `.md` files,
subsituting every occurrence of `task` with `thread`. In the `.rs`
files, only the texts in the comment blocks were affected.
|
|
|
|
This API was exercised in a few tests and mirrors the `from_str_radix`
functionality of the integer types.
Conflicts:
src/doc/trpl/traits.md
src/libstd/sys/windows/fs2.rs
|
|
"as an library" -> "as a library"
|
|
Link spanned a line and was missing the actual link target.
|
|
Had a newline in middle of a link, causing the link text to be shown with `[]`.
|
|
the code block in the no-stdlib.md file caused test failure on bitrig and openbsd.
Closes #24108
|
|
"as an library" -> "as a library"
|
|
Link spanned a line and was mising the actual link target.
|
|
Had a newline in middle of a link, causing the link text to be shown with `[]`.
|
|
|
|
Conflicts:
src/libstd/thread/mod.rs
src/test/bench/shootout-mandelbrot.rs
src/test/bench/shootout-reverse-complement.rs
src/test/run-pass/capturing-logging.rs
src/test/run-pass/issue-9396.rs
src/test/run-pass/tcp-accept-stress.rs
src/test/run-pass/tcp-connect-timeouts.rs
src/test/run-pass/tempfile.rs
|
|
Not sure if `From<Error>` is the correct way to reference that trait (maybe `From<E: Error>`?)
r? @steveklabnik
|
|
The two-step command left off the nightly flag :frown:
Thanks @mdinger
|
|
Feel silly because it's just one thing but it was bothering me that the documentation tells you what you're not going to learn now instead of linking to the item in question. Am total noob pls assist, where is power button. :)
|
|
Remove arity link from enums.md
r? @steveklabnik
|
|
Three more sections
|
|
|
|
|
|
|
|
Not sure if `From<Error>` is the correct way to reference that trait (maybe `From<E: Error>`?)
|
|
The two-step command left off the nightly flag :frown:
Thanks @mdinger
|
|
Feel silly because it's just one thing but it was bothering me that the documentation tells you what you're not going to learn now instead of linking to the item in question. Am total noob pls assist, where is power button. :)
|
|
|
|
|
|
|
|
|
|
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.
|
|
|
