macro call site go to definition

[xbz-24]

rust-analyzer version: (eg. output of "rust-analyzer: Show RA Version" command, accessible in VSCode via Ctrl/⌘+Shift+P)

rustc version: (eg. output of rustc -V)

editor or extension: (eg. VSCode, Vim, Emacs, etc. For VSCode users, specify your extension version; for users of other editors, provide the distribution if applicable)

relevant settings: (eg. client settings, or environment variables like CARGO, RUSTC, RUSTUP_HOME or CARGO_HOME)

repository link (if public, optional): (eg. rust-analyzer)

code snippet to reproduce:

// add your code here

mod cs {
        vulkano_shaders::shader! {
            ty: "compute",
            src: r"
            #version 460

            layout(local_size_x = 8, local_size_y = 8, local_size_z = 1) in;

            layout(set = 0, binding = 0, rgba8) uniform writeonly image2D img;

            void main() {
                vec2 norm_coordinates = (gl_GlobalInvocationID.xy + vec2(0.5)) / vec2(imageSize(img));
                vec2 c = (norm_coordinates - vec2(0.5)) * 2.0 - vec2(1.0, 0.0);

                vec2 z = vec2(0.0, 0.0);
                float i;
                for (i = 0.0; i < 1.0; i += 0.005) {
                    z = vec2(
                        z.x * z.x - z.y * z.y + c.x,
                        z.y * z.x + z.x * z.y + c.y
                    );

                    if (length(z) > 4.0) {
                        break;
                    }
                }

                vec4 to_write = vec4(vec3(i), 1.0);
                imageStore(img, ivec2(gl_GlobalInvocationID.xy), to_write);
            }
            ",
        }
    }

    let shader = cs::load(device.clone()).expect("failed to create shader module")

would be useful that go to definition takes you to the call site of the macro, right now this tells very little of the inner workings or what is going really right now.

Please let me know if someone cares about implementing this.

[Veykril]

What rust-analyzer version are you on? (There is a reason for the issue template existing, so it'd be nice if you filled that out...)

[xbz-24]

rust-analyzer --version
rust-analyzer 1.77.1 (7cf61ebd 2024-03-27)

this is the rust-analyzer's version, please let me know if there is a fix to this or not @Veykril

[xbz-24]

[xbz-24]

this is the rust-analyzer version vscode is using

[xbz-24]

rustc -V
rustc 1.77.1 (7cf61ebde 2024-03-27)

[xbz-24]

[Veykril]

Looks like we fail to resolve the extern prelude in local modules in block modules, it works fine if the mod cs is at the top-level (not nested inside a function or anything)

fn main() {
    mod f {
        use core as _;
    }
}

here core does not resolve

[xbz-24]

can someone fix this shit? it also happens with local modules when its outside of main

[lnicola]

Probably fixed in #17251.