Does not work for attribute proc macros

[dakyskye]

rust-analyzer does not work for this file:

use serenity::{
    client::*,
    framework::standard::{macros::command, Args, CommandResult},
    model::channel::Message,
};

#[command]
fn clear(ctx: &mut Context, msg: &Message, args: Args) -> CommandResult {
    Ok(())
}

No intellisense, no completion, nothing works. I assume it's because of command macro?

[lnicola]

Yes, attribute proc macros are not supported.

[lnicola]

I can't edit the issue title, can you rename it to something like the above?

CC #5412, #2984.

[flodiebold]

Most features should still work as if the attribute wasn't there though.

[lnicola]

@dakyskye can you confirm that completions are not working?

[dakyskye]

@lnicola yes

[lnicola]

Is that Vim? How did you configure rust-analyzer?

[dakyskye]

@lnicola it is NeoVim, yes, with coc.nvim extension. That's the only rust-analyser config I have "rust-analyzer.serverPath": "rust-analyzer"

[lnicola]

Can you run it (from the same terminal) with rust-analyzer --version? If you installed from source, it should be under ~/.cargo/bin, and I'd expect that to be in PATH, but it doesn't hurt to check.

[dakyskye]

Weird enough! My output for it is rust-analyzer ???????. I installed it from the Arch packages.

[dakyskye]

pacman -Q --info rust-analyzer outputs Version: 20200914-1

[lnicola]

Can you try https://github.com/fannheyward/coc-rust-analyzer/ instead? I think the official extension doesn't work too well with coc.nvim.

[dakyskye]

I use coc-rust-analyzer, but with custom rust-analyzer path.

[dakyskye]

I have also tried it in VSCode though, the same negative result.

[lnicola]

Does it work for you (in Code) with a new project?

[dakyskye]

Nope

[lnicola]

Sorry, I meant a new project as cargo new produces.

[dakyskye]

Yes, I did that.

[matklad]

Can't reproduce, maybe this is fixed in master?

[dakyskye]

It's weird. I have just tried it in VSCode, Vim and Emacs, works nowhere.
VSC result:

[dakyskye]

Ah, you said "master". I have latest release installed, let me build RA myself and try again.

EDIT: built rust-analyzer, but the result is same.

[matklad]

@dakyskye if you run Rust Analyzer: Status command, does it list anything as file deps?

[dakyskye]

I accidentally deleted vscode package, and just reinstalled it. Now rust-analyzer works well for me in VSC. Let me try it in Emacs now

[dakyskye]

It started working in VSCode, but still not working in Vim and Emacs.

[jmg-duarte]

I think this is the best place to put this issue.
I have a macro that adds a field to a struct.
For example:

#[add]
struct S;

Gets expanded to:

struct S { pub field: T }

While this compiles without a problem, rust-analyzer reports: no such field.
So, my issue is not about autocomplete, it's just about making the analyzer view the expansion result.

[bjorn3]

Missing autocompletion is just a symptom of the fact that attribute proc macros are currently unimplemented.

[DanielJoyce]

Yeah, would this explain why mockall_double #[double] macro doesn't work? Cargo check works, but rust analyzer gets confused and looks for Mock type not actual type outside test code.

[sanfusu]

Are there any plans to support this feature？

[abreis]

Yes, it's on the roadmap for the next six weeks: #8486

[dakyskye]

Oh, finally 🎉 🎉