| Age | Commit message (Collapse) | Author | Lines | |
|---|---|---|---|---|
| 2019-08-29 | Run doctests via out-of-process rustc | Andreas Jonson | -5/+2 | |
| 2019-08-27 | Rollup merge of #62600 - emmericp:libtest-add-show-output, r=gnzlbg | Mazdak Farrokhzad | -1/+1 | |
| libtest: add --show-output flag to print stdout of successful tests This pull request adds a new flag `--show-output` for tests to show the output of successful tests. For most formatters this was already supported just not exposed via the CLI (apparently only used by `librustdoc`). I've also added support for this option in the JSON formatter. This kind of fixes https://github.com/rust-lang/rust/issues/54669 which wants `--format json` to work with `--nocapture`, which is... well, impossible. What this issue really calls for is `--show-output` as implemented here. | ||||
| 2019-08-11 | Drop RefCell from IdMap in markdown rendering | Mark Rousskov | -3/+2 | |
| 2019-08-11 | Remove thread-local for playground config | Mark Rousskov | -5/+6 | |
| 2019-07-11 | libtest: add --show-output option | Paul Emmerich | -1/+1 | |
| this new flag enables printing the captured stdout of successful tests utilizing the already existing display_output test runner option | ||||
| 2019-07-01 | Remove needless lifetimes | Jeremy Stucki | -1/+1 | |
| 2019-05-06 | set the default edition when pre-parsing a doctest | QuietMisdreavus | -3/+9 | |
| 2019-04-22 | upgrade rustdoc's pulldown-cmark to 0.4.1 | Andy Russell | -4/+3 | |
| 2019-03-10 | Make the rustc driver and interface demand driven | John Kåre Alsaker | -2/+2 | |
| 2019-02-23 | Transition librustdoc to 2018 edition | Hirokazu Hata | -8/+6 | |
| 2019-02-10 | rustc: doc comments | Alexander Regueiro | -1/+1 | |
| 2019-01-17 | Persist doc test executables to given path. | Wesley Norris | -1/+1 | |
| 2018-12-25 | Remove licenses | Mark Rousskov | -10/+0 | |
| 2018-12-12 | Bump to 1.33.0 | Alex Crichton | -1/+1 | |
| * Update bootstrap compiler * Update version to 1.33.0 * Remove some `#[cfg(stage0)]` annotations Actually updating the version number is blocked on updating Cargo | ||||
| 2018-12-07 | Various minor/cosmetic improvements to code | Alexander Regueiro | -2/+2 | |
| 2018-11-02 | pass the Options struct instead of individual args | QuietMisdreavus | -27/+24 | |
| 2018-11-02 | swap uses of Matches with pre-parsed args | QuietMisdreavus | -6/+5 | |
| 2018-11-02 | parse command-line into a central Options struct | QuietMisdreavus | -2/+2 | |
| 2018-10-21 | Use markdown::render instead of using pulldown_cmark directly | Guillaume Gomez | -1/+1 | |
| 2018-08-19 | mv (mod) codemap source_map | Donato Sciarra | -1/+1 | |
| 2018-07-31 | Remove global derive_id and reset_ids functions | Mark Rousskov | -6/+5 | |
| Previously these functions relied on TLS but we can instead thread the relevant state through explicitly. | ||||
| 2018-07-31 | Further extract error code switch | Mark Rousskov | -4/+7 | |
| Removes dependency on UnstableFeatures from markdown rendering | ||||
| 2018-07-31 | Remove dependency on error handling from find_testable_code | Mark Rousskov | -1/+5 | |
| 2018-07-31 | Provide warnings for invalid code blocks in markdown files | Mark Rousskov | -1/+1 | |
| Previously we would only warn on Rust code but we can also do so when testing markdown (the diag::Handler is available). | ||||
| 2018-07-27 | Prefer to_string() to format!() | ljedrz | -2/+2 | |
| 2018-05-14 | replace error/warning println with structured diag | QuietMisdreavus | -7/+8 | |
| 2018-04-13 | add -C parameter to rustdoc | QuietMisdreavus | -3/+4 | |
| 2018-04-02 | suppress the default allow(unused) under --display-warnings | QuietMisdreavus | -0/+1 | |
| 2018-03-28 | use --edition for doctests, rather than just the crate | QuietMisdreavus | -2/+3 | |
| 2018-03-18 | Add warning for invalid start of code blocks in rustdoc | Guillaume Gomez | -1/+1 | |
| 2018-02-16 | Remove hoedown from rustdoc | Guillaume Gomez | -51/+11 | |
| Is it really time? Have our months, no, *years* of suffering come to an end? Are we finally able to cast off the pall of Hoedown? The weight which has dragged us down for so long? ----- So, timeline for those who need to catch up: * Way back in December 2016, [we decided we wanted to switch out the markdown renderer](https://github.com/rust-lang/rust/issues/38400). However, this was put on hold because the build system at the time made it difficult to pull in dependencies from crates.io. * A few months later, in March 2017, [the first PR was done, to switch out the renderers entirely](https://github.com/rust-lang/rust/pull/40338). The PR itself was fraught with CI and build system issues, but eventually landed. * However, not all was well in the Rustdoc world. During the PR and shortly after, we noticed [some differences in the way the two parsers handled some things](https://github.com/rust-lang/rust/issues/40912), and some of these differences were major enough to break the docs for some crates. * A couple weeks afterward, [Hoedown was put back in](https://github.com/rust-lang/rust/pull/41290), at this point just to catch tests that Pulldown was "spuriously" running. This would at least provide some warning about spurious tests, rather than just breaking spontaneously. * However, the problems had created enough noise by this point that just a few days after that, [Hoedown was switched back to the default](https://github.com/rust-lang/rust/pull/41431) while we came up with a solution for properly warning about the differences. * That solution came a few weeks later, [as a series of warnings when the HTML emitted by the two parsers was semantically different](https://github.com/rust-lang/rust/pull/41991). But that came at a cost, as now rustdoc needed proc-macro support (the new crate needed some custom derives farther down its dependency tree), and the build system was not equipped to handle it at the time. It was worked on for three months as the issue stumped more and more people. * In that time, [bootstrap was completely reworked](https://github.com/rust-lang/rust/pull/43059) to change how it ordered compilation, and [the method by which it built rustdoc would change](https://github.com/rust-lang/rust/pull/43482), as well. This allowed it to only be built after stage1, when proc-macros would be available, allowing the "rendering differences" PR to finally land. * The warnings were not perfect, and revealed a few [spurious](https://github.com/rust-lang/rust/pull/44368) [differences](https://github.com/rust-lang/rust/pull/45421) between how we handled the renderers. * Once these were handled, [we flipped the switch to turn on the "rendering difference" warnings all the time](https://github.com/rust-lang/rust/pull/45324), in October 2017. This began the "warning cycle" for this change, and landed in stable in 1.23, on 2018-01-04. * Once those warnings hit stable, and after a couple weeks of seeing whether we would get any more reports than what we got from sitting on nightly/beta, [we switched the renderers](https://github.com/rust-lang/rust/pull/47398), making Pulldown the default but still offering the option to use Hoedown. And that brings us to the present. We haven't received more new issues from this in the meantime, and the "switch by default" is now on beta. Our reasoning is that, at this point, anyone who would have been affected by this has run into it already. | ||||
| 2018-01-22 | Add LinkReplacer pass for pulldown | Manish Goregaokar | -1/+1 | |
| 2017-12-14 | Use PathBuf instead of String where applicable | Oliver Schneider | -8/+7 | |
| 2017-12-07 | fix markdown file differences | Guillaume Gomez | -12/+4 | |
| 2017-12-07 | Generate difference warnings for markdown files as well | Guillaume Gomez | -6/+47 | |
| 2017-10-15 | rustbuild: Support specifying archiver and linker explicitly | Vadim Petrochenkov | -2/+2 | |
| 2017-09-28 | Migrate to eprint/eprintln macros where appropriate. | Corey Farwell | -11/+3 | |
| 2017-07-06 | rustdoc: Don't run Markdown tests twice | Oliver Middleton | -2/+6 | |
| This matches the behaviour for finding tests in Rust files. | ||||
| 2017-05-05 | Add Options type in libtest and remove argument | Guillaume Gomez | -4/+2 | |
| 2017-05-02 | Add option to display warnings in rustdoc | Guillaume Gomez | -1/+4 | |
| 2017-04-22 | Re-enable hoedown by default | Guillaume Gomez | -5/+9 | |
| 2017-04-17 | Hoedown big comeback! | Guillaume Gomez | -1/+2 | |
| 2017-04-06 | rustdoc: Use pulldown-cmark for Markdown HTML rendering | Oliver Middleton | -2/+2 | |
| Instead of rendering all of the HTML in rustdoc this relies on pulldown-cmark's `push_html` to do most of the work. A few iterator adapters are used to make rustdoc specific modifications to the output. This also fixes MarkdownHtml and link titles in plain_summary_line. | ||||
| 2017-03-29 | Auto merge of #40338 - GuillaumeGomez:pulldown-switch, r=frewsxcv,steveklabnik | bors | -2/+2 | |
| Replace hoedown with pull in rustdoc cc @rust-lang/docs | ||||
| 2017-03-28 | Add missing markdown tags | Guillaume Gomez | -2/+2 | |
| 2017-03-28 | End of pulldown switch and remove completely hoedown | Guillaume Gomez | -1/+1 | |
| 2017-03-25 | rustdoc to accept `#` at the start of a markdown file #40560 | projektir | -5/+7 | |
| 2017-02-13 | Add filename when running rustdoc --test on a markdown file | Guillaume Gomez | -1/+2 | |
| 2017-02-06 | Display correct filename with --test option | Guillaume Gomez | -3/+3 | |
| 2017-02-03 | Switch logic to Span instead of HashMap | Guillaume Gomez | -2/+3 | |
