| Age | Commit message (Collapse) | Author | Lines |
|---|
|
|
|
The previous fix introduced in 75d49c8203405ab0af7a2b8b8698af02868fdbc2 neglected to parse outer attributes as described in #17782.
|
|
Rustdoc would previously improperly handle key="value" style cfgs, which
are notably used for Cargo features.
|
|
Because my '30 minute intro' was originally a blog post, the tone was a bit too light. It also was written a long time ago, and deserves a bit of a refresher for modern Rust. now that my work on the Guide is wrapping up, I want to give it a quick re-write as well.
This is not yet done, but I'm submitting it for feedback so far. I'd really like some comments on the ownership part in particular, which gets lower level than before, but is not strictly 100% accurate. Trying to strike a balance.
In general, I'm not sure I go into enough detail for those without systems experience, but am afraid of too much detail for those that do.
Rendered view: https://github.com/steveklabnik/rust/blob/intro_redux/src/doc/intro.md
/cc @wycats @nikomatsakis @brson etc
|
|
|
|
Adds a high-level discussion of "what collection should you use for what", as well as some general discussion of correct/efficient usage of the capacity, iterator, and entry APIs.
Still building docs to confirm this renders right and the examples are good, but the content can be reviewed now.
|
|
r? @aturon
|
|
[Previously](https://github.com/rust-lang/rust/commit/e5da6a71a6a0b46dd3630fc8326e6d5906a1fde6), the `Any` trait was split into a private portion and an (empty) public portion, in order to hide the implementation strategy used for downcasting. However, the [new rules](https://github.com/rust-lang/rust/commit/e9ad12c0cae5c43ada6641c7dc840a0fbe5010a2) for privacy forbid `AnyPrivate` from actually being private.
This patch thus reverts the introduction of `AnyPrivate`.
Although this is unlikely to break any real code, it removes a public trait and is therefore a:
[breaking-change]
|
|
|
|
|
|
|
|
|
|
|
|
[breaking-change]
If you are using slicing syntax you will need to add #![feature(slicing_syntax)] to your crate.
|
|
|
|
Rustdoc would previously improperly handle key="value" style cfgs, which
are notably used for Cargo features.
|
|
|
|
[Previously](https://github.com/rust-lang/rust/commit/e5da6a71a6a0b46dd3630fc8326e6d5906a1fde6),
the `Any` trait was split into a private portion and an (empty) public
portion, in order to hide the implementation strategy used for
downcasting. However, the [new
rules](https://github.com/rust-lang/rust/commit/e9ad12c0cae5c43ada6641c7dc840a0fbe5010a2)
for privacy forbid `AnyPrivate` from actually being private.
This patch thus reverts the introduction of `AnyPrivate`.
Although this is unlikely to break any real code, it removes a public
trait and is therefore a:
[breaking-change]
|
|
|
|
r=alexcrichton
Add example to doc for `slice::ImmutableSlice::binary_search`.
Fix #17817.
|
|
|
|
|
|
This PR adds support in rustdoc for properly naming lifetimes in bounds, instead of just showing `'static` for everything. It also adds support for unboxed function sugar bounds, which were also previously rendered as `'static`.
|
|
Previously, external code might call `markdown::render()` without having
called `markdown::reset_headers()`, meaning the TLS key
`used_header_map` was unset. Now `markdown::render()` ensures that
`used_header_map` is set by calling `reset_headers` if necessary.
Fix #17736
|
|
Fixes #17782.
|
|
Fix #17817.
|
|
Fix #17818
|
|
|
|
This includes optimizations to the thread cache and support for
shrinking and expanding huge (>4M) allocations in-place.
|
|
|
|
This closes issue #17021.
|
|
|
|
Fix #16518
|
|
Previously, external code might call `markdown::render()` without having
called `markdown::reset_headers()`, meaning the TLS key
`used_header_map` was unset. Now `markdown::render()` ensures that
`used_header_map` is set by calling `reset_headers` if necessary.
Fix #17736
|
|
Closes #17773.
|
|
|
|
|
|
For example, this renames `GroupRWX` to `GROUP_RWX`, and deprecates the old
name. Code using these statics should be updated accordingly.
|
|
Fixes #17405.
Fixes #17518.
Fixes #17800.
|
|
This includes optimizations to the thread cache and support for
shrinking and expanding huge (>4M) allocations in-place.
|
|
|
|
|
|
|
|
Fixes #17405.
Fixes #17518.
Fixes #17800.
|
|
This causes it to hit the previously ICEing debuginfo codepath
|
|
This fixes an ICE. Closes issue #17021
|
|
Closes issue #17734
r? @nick29581
|
|
|
|
Probably fallen through the cracks in #17630.
|
|
|
