about summary refs log tree commit diff
path: root/compiler/rustc_mir_transform/src
diff options
context:
space:
mode:
authorMatthias Krüger <matthias.krueger@famsik.de>2022-01-30 00:04:15 +0100
committerGitHub <noreply@github.com>2022-01-30 00:04:15 +0100
commit605ffd6113dc49a9b10ea2b5aa6ca41a275bb9ad (patch)
tree3cd698034f471c7dda9cb4e746684b6c41e17e64 /compiler/rustc_mir_transform/src
parent329753e24867a5dd8a3c0467e220ef28878d118c (diff)
parent3903ca197e55f209b2415e566b4b8f407f6fe899 (diff)
downloadrust-605ffd6113dc49a9b10ea2b5aa6ca41a275bb9ad.tar.gz
rust-605ffd6113dc49a9b10ea2b5aa6ca41a275bb9ad.zip
Rollup merge of #93441 - notriddle:notriddle/collect-crate-doc-links-very-early, r=petrochenkov
rustdoc: load the set of in-scope traits for modules with no docstring

Fixes #93428

This fix is a response to a couple of special cases related to the `module_id`, which is eventually used for trait candidates:

  * The module id is always set to the current crate, when checking `crate::`.

    Normally, the set of in-scope traits would be set in `load_links_in_attrs`, but if there are no doc comments, then that loop will never run.

  * the module id is set to the parent module, when resolving a module that is spelled like this:

        // Notice how we use an outlined doc comment here!
        // [`Test::my_fn`]
        mod something {
        }

    As with the above problem with `crate::`, we need to make sure the module gets its traits in scope resolved, even if it has no doc comments of its own.
Diffstat (limited to 'compiler/rustc_mir_transform/src')
0 files changed, 0 insertions, 0 deletions