rust/tests/rustdoc-ui/intra-doc/macro-rules.rs

//@ check-pass
#![allow(rustdoc::private_intra_doc_links)]

macro_rules! foo {
    () => {};
}

/// [foo!]
pub fn baz() {}

#[macro_use]
mod macros {
    macro_rules! escaping {
        () => {};
    }
}

pub mod inner {
    /// [foo!]
    /// [escaping]
    pub fn baz() {
        foo!();
    }
}
[AUTO_GENERATED] Migrate compiletest to use `ui_test`-style `//@` directives 2024-02-22 12:10:29 +00:00			`//@ check-pass`
rustdoc: Special-case macro lookups less Previously, rustdoc had 3 fallbacks it used: 1. `resolve_macro_path` 2. `all_macros` 3. `resolve_str_path_error` Ideally, it would only use `resolve_str_path_error`, to be consistent with other namespaces. Unfortunately, that doesn't consider macros that aren't defined at module scope; consider for instance ```rust { struct S; macro_rules! mac { () => {} } // `mac`'s scope starts here /// `mac` <- `resolve_str_path_error` won't see this struct Z; //`mac`'s scope ends here } ``` This changes it to only use `all_macros` and `resolve_str_path_error`, and gives `resolve_str_path_error` precedence over `all_macros` in case there are two macros with the same name in the same module. This also adds a failing test case which will catch trying to remove `all_macros`. 2022-02-06 18:39:42 -06:00			`#![allow(rustdoc::private_intra_doc_links)]`

			`macro_rules! foo {`
			`() => {};`
			`}`

			`/// [foo!]`
			`pub fn baz() {}`
rustdoc: Track `macro_rules` scopes during early doc link resolution This way links referring to `macro_rules` items are resolved correctly 2022-04-28 15:52:54 +03:00
			`#[macro_use]`
			`mod macros {`
			`macro_rules! escaping {`
			`() => {};`
			`}`
			`}`

			`pub mod inner {`
			`/// [foo!]`
			`/// [escaping]`
			`pub fn baz() {`
			`foo!();`
			`}`
			`}`