mikros/rust
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
73fd453f55
rust/tests/rustdoc-ui/intra-doc/prim-conflict.stderr

Ignoring revisions in .git-blame-ignore-revs. Click here to bypass and see the normal blame view.

60 lines
1.4 KiB
Plaintext
Raw Normal View History

Update UI tests for primitive type ambiguity error renaming
2023-03-24 08:50:12 -05:00
error: `char` is both a module and a primitive type
Move `src/test/rustdoc-ui` intra-doc tests into a subdirectory 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.
2020-11-28 20:10:37 -06:00
--> $DIR/prim-conflict.rs:4:6
Report an ambiguity if both modules and primitives are in scope - Add a new `prim@` disambiguator, since both modules and primitives are in the same namespace - Refactor `report_ambiguity` into a closure Additionally, I noticed that rustdoc would previously allow `[struct@char]` if `char` resolved to a primitive (not if it had a DefId). I fixed that and added a test case.
2020-08-22 14:00:19 -05:00
|
LL | /// [char]
| ^^^^ ambiguous link
|
note: the lint level is defined here
Move `src/test/rustdoc-ui` intra-doc tests into a subdirectory 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.
2020-11-28 20:10:37 -06:00
--> $DIR/prim-conflict.rs:1:9
Report an ambiguity if both modules and primitives are in scope - Add a new `prim@` disambiguator, since both modules and primitives are in the same namespace - Refactor `report_ambiguity` into a closure Additionally, I noticed that rustdoc would previously allow `[struct@char]` if `char` resolved to a primitive (not if it had a DefId). I fixed that and added a test case.
2020-08-22 14:00:19 -05:00
|
Rename rustdoc lints to be a tool lint instead of built-in. - 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-12-29 22:16:16 -06:00
LL | #![deny(rustdoc::broken_intra_doc_links)]
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Say 'prefix with `kind@`' instead of 'prefix with the item kind' This is both more specific and easier to read.
2020-08-27 23:53:36 -05:00
help: to link to the module, prefix with `mod@`
Report an ambiguity if both modules and primitives are in scope - Add a new `prim@` disambiguator, since both modules and primitives are in the same namespace - Refactor `report_ambiguity` into a closure Additionally, I noticed that rustdoc would previously allow `[struct@char]` if `char` resolved to a primitive (not if it had a DefId). I fixed that and added a test case.
2020-08-22 14:00:19 -05:00
|
Unify error reporting for intra-doc links - Give a suggestion even if there is no span available - Give a more accurate description of the change than 'use the disambiguator' - Write much less code
2020-08-25 15:21:02 -05:00
LL | /// [mod@char]
Modify structured suggestion output * On suggestions that include deletions, use a diff inspired output format * When suggesting addition, use `+` as underline * Color highlight modified span
2021-06-21 21:07:19 -05:00
| ++++
Update UI tests for primitive type ambiguity error renaming
2023-03-24 08:50:12 -05:00
help: to link to the primitive type, prefix with `prim@`
Report an ambiguity if both modules and primitives are in scope - Add a new `prim@` disambiguator, since both modules and primitives are in the same namespace - Refactor `report_ambiguity` into a closure Additionally, I noticed that rustdoc would previously allow `[struct@char]` if `char` resolved to a primitive (not if it had a DefId). I fixed that and added a test case.
2020-08-22 14:00:19 -05:00
|
LL | /// [prim@char]
Modify structured suggestion output * On suggestions that include deletions, use a diff inspired output format * When suggesting addition, use `+` as underline * Color highlight modified span
2021-06-21 21:07:19 -05:00
| +++++
Report an ambiguity if both modules and primitives are in scope - Add a new `prim@` disambiguator, since both modules and primitives are in the same namespace - Refactor `report_ambiguity` into a closure Additionally, I noticed that rustdoc would previously allow `[struct@char]` if `char` resolved to a primitive (not if it had a DefId). I fixed that and added a test case.
2020-08-22 14:00:19 -05:00
Update UI tests for primitive type ambiguity error renaming
2023-03-24 08:50:12 -05:00
error: `char` is both a module and a primitive type
Move `src/test/rustdoc-ui` intra-doc tests into a subdirectory 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.
2020-11-28 20:10:37 -06:00
--> $DIR/prim-conflict.rs:10:6
Report an ambiguity if both modules and primitives are in scope - Add a new `prim@` disambiguator, since both modules and primitives are in the same namespace - Refactor `report_ambiguity` into a closure Additionally, I noticed that rustdoc would previously allow `[struct@char]` if `char` resolved to a primitive (not if it had a DefId). I fixed that and added a test case.
2020-08-22 14:00:19 -05:00
|
LL | /// [type@char]
| ^^^^^^^^^ ambiguous link
|
Say 'prefix with `kind@`' instead of 'prefix with the item kind' This is both more specific and easier to read.
2020-08-27 23:53:36 -05:00
help: to link to the module, prefix with `mod@`
Report an ambiguity if both modules and primitives are in scope - Add a new `prim@` disambiguator, since both modules and primitives are in the same namespace - Refactor `report_ambiguity` into a closure Additionally, I noticed that rustdoc would previously allow `[struct@char]` if `char` resolved to a primitive (not if it had a DefId). I fixed that and added a test case.
2020-08-22 14:00:19 -05:00
|
Unify error reporting for intra-doc links - Give a suggestion even if there is no span available - Give a more accurate description of the change than 'use the disambiguator' - Write much less code
2020-08-25 15:21:02 -05:00
LL | /// [mod@char]
Modify structured suggestion output * On suggestions that include deletions, use a diff inspired output format * When suggesting addition, use `+` as underline * Color highlight modified span
2021-06-21 21:07:19 -05:00
| ~~~~
Update UI tests for primitive type ambiguity error renaming
2023-03-24 08:50:12 -05:00
help: to link to the primitive type, prefix with `prim@`
Report an ambiguity if both modules and primitives are in scope - Add a new `prim@` disambiguator, since both modules and primitives are in the same namespace - Refactor `report_ambiguity` into a closure Additionally, I noticed that rustdoc would previously allow `[struct@char]` if `char` resolved to a primitive (not if it had a DefId). I fixed that and added a test case.
2020-08-22 14:00:19 -05:00
|
LL | /// [prim@char]
Modify structured suggestion output * On suggestions that include deletions, use a diff inspired output format * When suggesting addition, use `+` as underline * Color highlight modified span
2021-06-21 21:07:19 -05:00
| ~~~~~
Report an ambiguity if both modules and primitives are in scope - Add a new `prim@` disambiguator, since both modules and primitives are in the same namespace - Refactor `report_ambiguity` into a closure Additionally, I noticed that rustdoc would previously allow `[struct@char]` if `char` resolved to a primitive (not if it had a DefId). I fixed that and added a test case.
2020-08-22 14:00:19 -05:00
error: incompatible link kind for `char`
Move `src/test/rustdoc-ui` intra-doc tests into a subdirectory 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.
2020-11-28 20:10:37 -06:00
--> $DIR/prim-conflict.rs:19:6
Report an ambiguity if both modules and primitives are in scope - Add a new `prim@` disambiguator, since both modules and primitives are in the same namespace - Refactor `report_ambiguity` into a closure Additionally, I noticed that rustdoc would previously allow `[struct@char]` if `char` resolved to a primitive (not if it had a DefId). I fixed that and added a test case.
2020-08-22 14:00:19 -05:00
|
LL | /// [struct@char]
Update rustdoc-ui tests for intra-doc links errors
2021-07-19 10:00:35 -05:00
| ^^^^^^^^^^^ this link resolved to a module, which is not a struct
Report an ambiguity if both modules and primitives are in scope - Add a new `prim@` disambiguator, since both modules and primitives are in the same namespace - Refactor `report_ambiguity` into a closure Additionally, I noticed that rustdoc would previously allow `[struct@char]` if `char` resolved to a primitive (not if it had a DefId). I fixed that and added a test case.
2020-08-22 14:00:19 -05:00
|
Update rustdoc-ui tests for intra-doc links errors
2021-07-19 10:00:35 -05:00
help: to link to the module, prefix with `mod@`
|
LL | /// [mod@char]
Modify structured suggestion output * On suggestions that include deletions, use a diff inspired output format * When suggesting addition, use `+` as underline * Color highlight modified span
2021-06-21 21:07:19 -05:00
| ~~~~
Report an ambiguity if both modules and primitives are in scope - Add a new `prim@` disambiguator, since both modules and primitives are in the same namespace - Refactor `report_ambiguity` into a closure Additionally, I noticed that rustdoc would previously allow `[struct@char]` if `char` resolved to a primitive (not if it had a DefId). I fixed that and added a test case.
2020-08-22 14:00:19 -05:00
error: incompatible link kind for `char`
Move `src/test/rustdoc-ui` intra-doc tests into a subdirectory 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.
2020-11-28 20:10:37 -06:00
--> $DIR/prim-conflict.rs:26:10
Report an ambiguity if both modules and primitives are in scope - Add a new `prim@` disambiguator, since both modules and primitives are in the same namespace - Refactor `report_ambiguity` into a closure Additionally, I noticed that rustdoc would previously allow `[struct@char]` if `char` resolved to a primitive (not if it had a DefId). I fixed that and added a test case.
2020-08-22 14:00:19 -05:00
|
LL | //! [struct@char]
Update UI tests for primitive type ambiguity error renaming
2023-03-24 08:50:12 -05:00
| ^^^^^^^^^^^ this link resolved to a primitive type, which is not a struct
Update rustdoc-ui tests for intra-doc links errors
2021-07-19 10:00:35 -05:00
|
Update UI tests for primitive type ambiguity error renaming
2023-03-24 08:50:12 -05:00
help: to link to the primitive type, prefix with `prim@`
Report an ambiguity if both modules and primitives are in scope - Add a new `prim@` disambiguator, since both modules and primitives are in the same namespace - Refactor `report_ambiguity` into a closure Additionally, I noticed that rustdoc would previously allow `[struct@char]` if `char` resolved to a primitive (not if it had a DefId). I fixed that and added a test case.
2020-08-22 14:00:19 -05:00
|
Update rustdoc-ui tests for intra-doc links errors
2021-07-19 10:00:35 -05:00
LL | //! [prim@char]
Modify structured suggestion output * On suggestions that include deletions, use a diff inspired output format * When suggesting addition, use `+` as underline * Color highlight modified span
2021-06-21 21:07:19 -05:00
| ~~~~~
Report an ambiguity if both modules and primitives are in scope - Add a new `prim@` disambiguator, since both modules and primitives are in the same namespace - Refactor `report_ambiguity` into a closure Additionally, I noticed that rustdoc would previously allow `[struct@char]` if `char` resolved to a primitive (not if it had a DefId). I fixed that and added a test case.
2020-08-22 14:00:19 -05:00
error: aborting due to 4 previous errors
Reference in New Issue Copy Permalink