| Age | Commit message (Collapse) | Author | Lines |
|---|
|
Removes extra "the" from the phrase "the the Rust Programming Language
book", which isn't particularly grammatical.
|
|
There are hundreds of stackoverflow answers, reddit posts and blog
articles that link to these documents, so it's a nicer user experience
if they're not plain 404s.
The intention is to let these hang around only for relatively short
while. The alpha is likely to bring in many new users and they will be
reading the documents mentioned above.
|
|
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.
|
|
|
|
Fix a typo in guide
Reviewed-by: steveklabnik
|
|
Fix type annotation in guide
Reviewed-by: steveklabnik
|
|
Use a better word in the guide
Reviewed-by: steveklabnik
|
|
|
|
|
|
|
|
|
|
Number of rustc calls would depending on various circumstances. Two is misleading.
|
|
|
|
|
|
doc: Add missing `$`s in the Installing Rust guide
Reviewed-by: steveklabnik, steveklabnik
|
|
Update guide for Cargo installation
Reviewed-by: steveklabnik
|
|
Fix typo in documentation.
Reviewed-by: alexcrichton
|
|
Make all integers in the guide `i32`, implicitely
Reviewed-by: steveklabnik
|
|
doc: mailing list is deprecated
Reviewed-by: brson
|
|
|
|
|
|
The guide still needs to talk about integer suffixes.
|
|
|
|
A tuple could be more made up of more than 2 values. Update guide to reflect.
|
|
Number of rustc calls would depending on various circumstances. Two is misleading.
|
|
|
|
Nothing major. Clarification, copy-editing, typographical and grammatical consistency
|
|
Conflicts:
src/libstd/rt/exclusive.rs
src/libstd/sync/barrier.rs
src/libstd/sys/unix/pipe.rs
src/test/bench/shootout-binarytrees.rs
src/test/bench/shootout-fannkuch-redux.rs
|
|
Now that it's been removed from the prelude, we need to treat things differently.
Fixes #17967
|
|
This commit is an implementation of [RFC 503][rfc] which is a stabilization
story for the prelude. Most of the RFC was directly applied, removing reexports.
Some reexports are kept around, however:
* `range` remains until range syntax has landed to reduce churn.
* `Path` and `GenericPath` remain until path reform lands. This is done to
prevent many imports of `GenericPath` which will soon be removed.
* All `io` traits remain until I/O reform lands so imports can be rewritten all
at once to `std::io::prelude::*`.
This is a breaking change because many prelude reexports have been removed, and
the RFC can be consulted for the exact list of removed reexports, as well as to
find the locations of where to import them.
[rfc]: https://github.com/rust-lang/rfcs/blob/master/text/0503-prelude-stabilization.md
[breaking-change]
Closes #20068
|
|
This pass performs a second pass of stabilization through the `std::sync`
module, avoiding modules/types that are being handled in other PRs (e.g.
mutexes, rwlocks, condvars, and channels).
The following items are now stable
* `sync::atomic`
* `sync::atomic::ATOMIC_BOOL_INIT` (was `INIT_ATOMIC_BOOL`)
* `sync::atomic::ATOMIC_INT_INIT` (was `INIT_ATOMIC_INT`)
* `sync::atomic::ATOMIC_UINT_INIT` (was `INIT_ATOMIC_UINT`)
* `sync::Once`
* `sync::ONCE_INIT`
* `sync::Once::call_once` (was `doit`)
* C == `pthread_once(..)`
* Boost == `call_once(..)`
* Windows == `InitOnceExecuteOnce`
* `sync::Barrier`
* `sync::Barrier::new`
* `sync::Barrier::wait` (now returns a `bool`)
* `sync::Semaphore::new`
* `sync::Semaphore::acquire`
* `sync::Semaphore::release`
The following items remain unstable
* `sync::SemaphoreGuard`
* `sync::Semaphore::access` - it's unclear how this relates to the poisoning
story of mutexes.
* `sync::TaskPool` - the semantics of a failing task and whether a thread is
re-attached to a thread pool are somewhat unclear, and the
utility of this type in `sync` is question with respect to
the jobs of other primitives. This type will likely become
stable or move out of the standard library over time.
* `sync::Future` - futures as-is have yet to be deeply re-evaluated with the
recent core changes to Rust's synchronization story, and will
likely become stable in the future but are unstable until
that time comes.
[breaking-change]
|
|
|
|
|
|
In the context of explaining the declaration of mutable bindings, using 'intended' probably conveys the meaning better than 'cared'.
|
|
Fixes #20088
|
|
In the context of explaining the declaration of mutable bindings, using 'intended' probably conveys the meaning better than 'cared'.
|
|
Updating curl flag and instructions to follow better security practices
used by other projects: https://github.com/saltstack/salt-bootstrap
Other references:
http://www.reddit.com/r/linux/comments/1s58my/please_stop_piping_curl1_to_sh1/
http://www.seancassidy.me/dont-pipe-to-your-shell.html
https://news.ycombinator.com/item?id=8550511
http://output.chrissnell.com/post/69023793377/stop-piping-curl-1-to-sh-1
http://www.reddit.com/comments/1pqtcb
|
|
For consistency with the documentation, *options* should be before *filenames*.
|
|
|
|
A part of #20038
This is just the beginning of what needs to be done, but it's some of it.
/cc @aturon
|
|
|
|
Fixes #20088
|
|
from curl manpage:
```
-O, --remote-name
Write output to a local file named like the remote file we get. (Only the file part
of the remote file is used, the path is cut off.)
```
|
|
Updating curl flag and instructions to follow better security practices
used by other projects: https://github.com/saltstack/salt-bootstrap
Other references:
http://www.reddit.com/r/linux/comments/1s58my/please_stop_piping_curl1_to_sh1/
http://www.seancassidy.me/dont-pipe-to-your-shell.html
https://news.ycombinator.com/item?id=8550511
http://output.chrissnell.com/post/69023793377/stop-piping-curl-1-to-sh-1
http://www.reddit.com/comments/1pqtcb
|
|
|
|
|
|
A part of #20038
|
|
|
|
|
|
Mostly copy-editing, clarification---in particular, monomorphization
|
