rust/src/test/rustdoc/auxiliary, branch 1.45.2

rustdoc supports const re-exports

2020-04-29T15:52:02+00:00

rustdoc: Don't try to load source files from external crates

2020-04-08T17:35:17+00:00

Local items defined in external macros shouldn't generate rendered source files and should link to the external crate's docs instead.

rustdoc: Fix re-exporting primitive types

2020-01-26T21:32:43+00:00

* Generate links to the primitive type docs for re-exports. * Don't ICE on cross crate primitive type re-exports. * Make primitive type re-exports show up cross crate.

rustdoc: Deliberately load extern crates before processing docs

2019-11-08T07:41:40+00:00

In order that we can successfully later resolve paths in crates which weren't loaded as a result of merely parsing the crate we're documenting, we force the resolution of the path to each crate before cloning the resolver to use later. Closes #66159 Signed-off-by: Daniel Silverstone

Auto merge of #63937 - Nashenas88:rustdoc_57180, r=GuillaumeGomez

2019-09-27T13:51:25+00:00

Fix ICE in rustdoc when merging generic and where bounds of an Fn with an output Fixes #57180

Add regression test for issue, apply suggestion to convert to assert_eq

2019-08-28T04:21:30+00:00

add regression test

2019-08-27T04:35:22+00:00

Remove double trailing newlines

2019-04-22T15:57:01+00:00

Auto merge of #58972 - QuietMisdreavus:intra-doc-link-imports, r=GuillaumeGomez

2019-04-11T08:48:26+00:00

rustdoc: don't process `Crate::external_traits` when collecting intra-doc links Part of https://github.com/rust-lang/rust/issues/58745, closes https://github.com/rust-lang/rust/pull/58917 The `collect-intra-doc-links` pass keeps track of the modules it recurses through as it processes items. This is used to know what module to give the resolver when looking up links. When looking through the regular items of the crate, this works fine, but the `DocFolder` trait as written doesn't just process the main crate hierarchy - it also processes the trait items in the `external_traits` map. This is useful for other passes (so they can strip out `#[doc(hidden)]` items, for example), but here it creates a situation where we're processing items "outside" the regular module hierarchy. Since everything in `external_traits` is defined outside the current crate, we can't fall back to finding its module scope like we do with local items. Skipping this collection saves us from emitting some spurious warnings. We don't even lose anything by skipping it, either - the docs loaded from here are only ever rendered through `html::render::document_short` which strips any links out, so the fact that the links haven't been loaded doesn't matter. Hopefully this removes most of the remaining spurious resolution warnings from intra-doc links. r? @GuillaumeGomez

Moved issue tests to subdirs and normalised names.

2019-03-14T01:00:49+00:00