about summary refs log tree commit diff
path: root/src/test/rustdoc-ui/intra-doc
AgeCommit message (Collapse)AuthorLines
2021-03-28Add test for weird backticks placementCamelid-8/+23
2021-03-28Point to disambiguator instead of whole linkCamelid-12/+5
And, now that we do that, we can remove the explanatory note since the error span should make it clear what the disambiguator is.
2021-03-26Lint on unknown intra-doc link disambiguatorsCamelid-0/+50
2021-03-22rustdoc: Record crate name instead of using `None`Camelid-0/+17
2021-03-01Rename rustdoc lints to be a tool lint instead of built-in.Joshua Nelson-39/+39
- Rename `broken_intra_doc_links` to `rustdoc::broken_intra_doc_links` - Ensure that the old lint names still work and give deprecation errors - Register lints even when running doctests Otherwise, all `rustdoc::` lints would be ignored. - Register all existing lints as removed This unfortunately doesn't work with `register_renamed` because tool lints have not yet been registered when rustc is running. For similar reasons, `check_backwards_compat` doesn't work either. Call `register_removed` directly instead. - Fix fallout + Rustdoc lints for compiler/ + Rustdoc lints for library/ Note that this does *not* suggest `rustdoc::broken_intra_doc_links` for `rustdoc::intra_doc_link_resolution_failure`, since there was no time when the latter was valid.
2021-02-19[intra-doc links] Don't check feature gates of items re-exported across cratesJoshua Nelson-0/+8
It should be never break another crate to re-export a public item. Note that this doesn't check the feature gate at *all* for other crates: - Feature-gates aren't currently serialized, so the only way to check the gate is with ad-hoc attribute checking. - Checking the feature gate twice (once when documenting the original crate and one when documenting the current crate) seems not great. This should still catch using the feature most of the time though, since people tend to document their own crates.
2021-02-11Fix private intra-doc warnings on associated itemsJoshua Nelson-5/+26
The issue was that the `kind, id` override was previously only being considered for the disambiguator check, not the privacy check. This uses the same ID for both.
2021-01-17Feature-gate `pointer` and `reference` in intra-doc linksJoshua Nelson-9/+39
- Only feature gate associated items - Add docs to unstable book
2021-01-08Rollup merge of #80372 - jyn514:fix-panics, r=ManishearthYuki Okushi-0/+20
Don't panic when an external crate can't be resolved This isn't actually a bug, it can occur when rustdoc tries to resolve a crate that isn't used in the main code. Fixes #72381. r? `@kinnison` if you have time, otherwise `@Manishearth`
2021-01-04fix incompatible disambiguator testmax-heller-0/+18
2020-12-25Don't panic when an external crate can't be resolvedJoshua Nelson-0/+20
This isn't actually a bug, it can occur when rustdoc tries to resolve a crate that isn't used in the main code.
2020-12-24Don't process `[]` and `()` in intra-doc linksJoshua Nelson-0/+103
These caused several false positives when documenting rustc, which means there will likely be many more false positives in the rest of the ecosystem.
2020-11-28Move `src/test/rustdoc-ui` intra-doc tests into a subdirectoryJoshua Nelson-0/+1262
This also changes the builder to allow using `x.py test src/test/rustdoc-ui/intra-doc`; before, it would panic that no paths were found.