| Age | Commit message (Collapse) | Author | Lines |
|---|
|
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
|
|
Fix checking of command line expansion spans
Reviewed-by: alexcrichton
|
|
Enabled the `vec![]` macro to use the `[a; b]` repeat syntax.
Reviewed-by: alexcrichton
|
|
|
|
Both `Extend::extend` and `DoubleEndedIterator::next_back` were intended to be
stable, but they mistakenly didn't have the `#[stable]` tag.
|
|
This adds an early return to skip code blocks without IDs.
Fixes #20864.
|
|
|
|
Closes #20711
|
|
keywords
|
|
|
|
|
|
There is likely to be new users with the alpha release, and there are a lot of documents on the internet (StackOverflow, reddit, blogs) that refer to these guides, so emitting a more helpful error than "404" is nice. Hence, I've temporarily reinstated stub documents for each of the old guides, referring to as relevant a part of the book as possible.
Also, rustbook was silently ignoring some errors, which lead to an inconsistency with directory creation/file writing. This meant the CSS file was not being written if no `doc` directory existed in the users build dir (e.g. the buildbots). This should mean that the CSS will appear automatically in later builds.
|
|
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!)
|
|
This will temporarily prevent warnings generated from expanding to code that the
test harness itself uses. This solution will require tweaking around the beta
cycle, but it will prevent spurious warnings for now.
Closes #20823
|
|
|
|
Both `Extend::extend` and `DoubleEndedIterator::next_back` were intended to be
stable, but they mistakenly didn't have the `#[stable]` tag.
|
|
|
|
r? @alexcrichton. This passes tests for me.
|
|
This will temporarily prevent warnings generated from expanding to code that the
test harness itself uses. This solution will require tweaking around the beta
cycle, but it will prevent spurious warnings for now.
Closes #20823
|
|
|
|
a type parameter for closures.
|
|
|
|
|
|
The libstd definitions move to libcore, which causes some minor updates there.
|
|
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.
|
|
|
|
Add test for issue #20414
Reviewed-by: alexcrichton
|
|
Make rustdoc use the `[_; N]` syntax instead of `[_, ..N]`
Reviewed-by: sfackler
|
|
Better iOS support
Reviewed-by: alexcrichton
|
|
Currently we pass a `struct S(u64)` as an immediate value on i686, but a
`struct S { x: u64 }` is passed indirectly. This seems pretty wrong,
as they both have the same underlying LLVM type `{ i64 }`, no sense in
treating them differently.
|
|
|
|
|
|
|
|
Changed alignment according to official Apple docs
|
|
Now it is possible to run tests on a jailbroken device
|
|
- target_word_size -> target_pointer_width
- added armv7 and armv7s targets
- enabled building binaries so tests could be run on a jailbroken device
|
|
|
|
The URL previously caused the book to require an internet connection to
get the full styling, this should mean no internet is required.
|
|
This reverts commit 6342aa62efd1b3aa7e1bc8f834f317290b11c519.
|
|
Fixes #19907
|
|
Silently ignoring errors is :( so lets not silently ignore them. huon is
:) now.
|
|
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.
|
|
|
|
Closes #20711
|
|
Because we are warning about unstable APIs and there are many
of these yet, this creates a high likelyhood doc tests will
fail.
This doesn't seem right as a blanket policy to me anyway, though
certainly we want it in std. Probably more appropriate to add
a rustdoc option.
|
|
|
