about summary refs log tree commit diff
path: root/src/test/rustdoc-ui/lint-group.stderr
AgeCommit message (Collapse)AuthorLines
2023-01-11Move /src/test to /testsAlbert Larsan-50/+0
2022-10-01bless rustdoc-uiMaybe Waffle-1/+1
2022-09-12Feature gate the rustdoc::missing_doc_code_examples lintWim Looman-6/+6
2022-03-25Bless rustdoc tests.Camille GILLOT-15/+0
2021-03-05Rename `rustdoc` to `rustdoc::all`Joshua Nelson-12/+12
When rustdoc lints were changed to be tool lints, the `rustdoc` group was removed, leading to spurious warnings like ``` warning: unknown lint: `rustdoc` ``` The lint group still worked when rustdoc ran, since rustdoc added the group itself. This renames the group to `rustdoc::all` for consistency with `clippy::all` and the rest of the rustdoc lints.
2021-03-01Rename rustdoc lints to be a tool lint instead of built-in.Joshua Nelson-4/+4
- 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.
2020-10-07Auto merge of #77119 - GuillaumeGomez:unclosed-html-tag-lint, r=jyn514bors-1/+20
Unclosed html tag lint Part of #67799. I think `@ollie27` will be interested (`@Manishearth` too since they opened the issue ;) ). r? `@jyn514`
2020-10-03Add test for invalid_html_tag lint in deny(rustdoc)Guillaume Gomez-1/+20
2020-10-02Improve error messagesCamelid-1/+1
2020-10-02Remove unhelpful help messageCamelid-1/+0
2020-10-02Improve rustdoc error for failed intra-doc link resolutionCamelid-1/+2
The previous error was confusing since it made it sound like you can't link to items that are defined outside the current module. Also suggested importing the item.
2020-09-23Perform most diagnostic lookups in `resolution_failure`Joshua Nelson-1/+1
Previously, these were spread throughout the codebase. This had two drawbacks: 1. It caused the fast path to be slower: even if a link resolved, rustdoc would still perform various lookups for the error diagnostic. 2. It was inconsistent and didn't always give all diagnostics (https://github.com/rust-lang/rust/issues/76925) Now, diagnostics only perform expensive lookups in the error case. Additionally, the error handling is much more consistent, both in wording and behavior. - Remove `CannotHaveAssociatedItems`, `NotInScope`, `NoAssocItem`, and `NotAVariant` in favor of the more general `NotResolved` `resolution_failure` will now look up which of the four above categories is relevant, instead of requiring the rest of the code to be consistent and accurate in which it picked. - Remove unnecessary lookups throughout the intra-doc link pass. These are now done by `resolution_failure`. + Remove unnecessary `extra_fragment` argument to `variant_field()`; it was only used to do lookups on failure. + Remove various lookups related to associated items + Remove distinction between 'not in scope' and 'no associated item' - Don't perform unnecessary copies - Remove unused variables and code - Update tests - Note why looking at other namespaces is still necessary - 'has no inner item' -> 'contains no item' bless tests
2020-09-11Name the current moduleJoshua Nelson-2/+1
'not in scope' -> 'not in `module`'
2020-09-05Make errors more concise and helpfulJoshua Nelson-1/+2
Before: ``` = note: this link partially resolves to the struct `S` = note: no `fmt` in `S` ``` After: ``` = note: the struct `S` has no field or associated item named `fmt` ```
2020-07-30intra_doc_resolution_failures -> broken_intra_doc_linksManish Goregaokar-1/+1
2020-07-30Rename to intra_doc_resolution_failuresManish Goregaokar-1/+1
2020-07-29Rename usage of intra_doc_link_resolution_failureManish Goregaokar-1/+1
2020-07-27Separate `missing_doc_code_examples` from intra-doc linksJoshua Nelson-13/+13
These two lints have no relation other than both being nightly-only. This allows stabilizing intra-doc links without stabilizing missing_doc_code_examples.
2020-07-20refactor and reword intra-doc link errorsAndy Russell-3/+3
This commit refactors intra-doc link error reporting to deduplicate code and decouple error construction from the type of error. This greatly improves flexibility at each error construction site, while reducing the complexity of the diagnostic creation. This commit also rewords the diagnostics for clarity and style: - Diagnostics should not end in periods. - It's unnecessary to say "ignoring it". Since this is a warning by default, it's already clear that the link is ignored.
2020-01-24Normalise notes with the/isvarkor-3/+3
2019-11-27Auto merge of #66675 - GuillaumeGomez:support-anchors-intra-doc-links, ↵bors-1/+1
r=kinnison Support anchors intra doc links Fixes #62833 Part of #43466. cc @ollie27 r? @kinnison
2019-11-25Update error messagesGuillaume Gomez-1/+1
2019-11-24Fix some rustdoc error capitalizationEsteban Küber-2/+2
2019-07-17normalize use of backticks in compiler messages for librustc/lintSamy Kacimi-3/+3
https://github.com/rust-lang/rust/issues/60532
2019-03-25compiletest: make path normalization smarterAndy Russell-1/+1
2019-03-10Make the rustc driver and interface demand drivenJohn Kåre Alsaker-0/+2
2018-12-25Remove licensesMark Rousskov-6/+6
2018-12-10add a lint group for lints emitted by rustdocQuietMisdreavus-0/+44
generated by cgit-pink 1.4.1-3-g733a5 (git 2.37.1) at 2026-03-01 20:19:45 +0000