| Age | Commit message (Collapse) | Author | Lines |
|
Replace `#[ignore(cfg(a, b))]` with `#[cfg_attr(all(a, b), ignore)]`
|
|
|
|
This breaks a fair amount of code. The typical patterns are:
* `for _ in range(0, 10)`: change to `for _ in range(0u, 10)`;
* `println!("{}", 3)`: change to `println!("{}", 3i)`;
* `[1, 2, 3].len()`: change to `[1i, 2, 3].len()`.
RFC #30. Closes #6023.
[breaking-change]
|
|
rustdoc now supports compiling things with `--test` so the examples in
this guide can be compiled & tested properly (revealing a few issues &
out-dated behaviours).
Also, reword an example to be clearer, cc #12242.
|
|
Now that rustdoc understands proper language tags
as the code not being Rust, we can tag everything
properly.
This change tags examples in other languages by
their language. Plain notations are marked as `text`.
Console examples are marked as `console`.
Also fix markdown.rs to not highlight non-rust code.
|
|
This is fully backwards compatible, since test names are Rust
identifiers + `:`, and hence not special regex characters.
Fixes #2866.
|
|
See #13476
|
|
|
|
Closes #12640
|
|
Closes #12702
|
|
The changes are basically just because rustdoc runs tests/rendering on
more snippets by default (i.e. everything without a `notrust` tag), and
not anything significant.
|
|
|
|
This was previously implemented, and it just needed a snapshot to go through
|
|
be more precise about what's being benchmarked.
Also, reorganise the layout a bit, to put examples directly in their
sections.
|
|
We generate documentation into the doc/ directory, so we shouldn't be
intermingling source files with generated files
|