rust/src/test/rustdoc-ui/failed-doctest-output.stdout, branch 1.44.0 https://github.com/rust-lang/rust http://git.dreamy.place/mirrors/rust/atom?h=1.44.0 2020-01-12T15:37:50+00:00 Update `output-default.json` and rustdoc test 2020-01-12T15:37:50+00:00 varkor github@varkor.com 2020-01-10T18:24:34+00:00 urn:sha1:1faa05daac8069503a0ffbba735db3b259424296 rustdoc: forward -Z options to rustc 2019-10-11T20:29:11+00:00 Tomasz Miąsko tomasz.miasko@gmail.com 2019-10-11T00:00:00+00:00 urn:sha1:5db17335a15e5e290bd7505cc37b2177c86b51c1 Currently rustdoc does not forward `-Z` options to rustc when building test executables. This makes impossible to use rustdoc to run test samples when crate under test is instrumented with one of sanitizers `-Zsanitizer=...`, since the final linking step will not include sanitizer runtime library. Forward `-Z` options to rustc to solve the issue. Helps with #43031. Improve Rustdoc's handling of procedural macros 2019-08-24T17:11:57+00:00 Aaron Hill aa1ronham@gmail.com 2019-07-20T20:34:41+00:00 urn:sha1:14986081355db0a2ae67df6a43dd9e6e360d718c Fixes #58700 Fixes #58696 Fixes #49553 Fixes #52210 This commit removes the special rustdoc handling for proc macros, as we can now retrieve their span and attributes just like any other item. A new command-line option is added to rustdoc: `--crate-type`. This takes the same options as rustc's `--crate-type` option. However, all values other than `proc-macro` are treated the same. This allows Rustdoc to enable 'proc macro mode' when handling a proc macro crate. In compiletest, a new 'rustdoc-flags' option is added. This allows us to pass in the '--proc-macro-crate' flag in the absence of Cargo. I've opened [an additional PR to Cargo](https://github.com/rust-lang/cargo/pull/7159) to support passing in this flag. These two PRS can be merged in any order - the Cargo changes will not take effect until the 'cargo' submodule is updated in this repository. Reblessed tests. 2019-06-05T20:09:27+00:00 Alexander Regueiro alexreg@me.com 2019-05-20T00:08:52+00:00 urn:sha1:10b6daa6c8e1e4b2a041c3a28cae8e1c139c1bd2 do not print panic message on doctest failures 2019-05-22T17:27:53+00:00 Andy Russell arussell123@gmail.com 2019-05-04T19:37:12+00:00 urn:sha1:89d437ec76cab8153ada936c5d67ef2deb901eb4 Move `edition` outside the hygiene lock and avoid accessing it 2019-05-21T16:17:05+00:00 John Kåre Alsaker john.kare.alsaker@gmail.com 2019-04-05T22:15:49+00:00 urn:sha1:a1f2dceaebd21a6f8a5f9341bf41724bb20e2a7d report fatal errors during doctest parsing 2019-04-24T04:03:53+00:00 Andy Russell arussell123@gmail.com 2019-04-23T21:39:26+00:00 urn:sha1:a912664113394fdf3a7c26a93504ebfe54a66e5c Make the rustc driver and interface demand driven 2019-03-10T03:49:45+00:00 John Kåre Alsaker john.kare.alsaker@gmail.com 2018-12-08T19:30:23+00:00 urn:sha1:51938c61f6f1b26e463f9071716f543543486e72 Introduce rustc_interface and move some methods there 2019-02-28T18:30:31+00:00 John Kåre Alsaker john.kare.alsaker@gmail.com 2018-12-08T19:30:23+00:00 urn:sha1:23a51f91c928a4ff2cbf39218e6e991365e5f562 rustdoc: Don't modify library path for doctests 2019-01-20T10:14:26+00:00 Oliver Middleton olliemail27@gmail.com 2019-01-20T10:14:26+00:00 urn:sha1:ad09d7fc794500709242d5b10daa6afd263d1410 It shouldn't be needed anymore because doctests are no longer compiled with `prefer-dynamic`.