You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If I improve goToReferences on function arguments by ignoring the tracing-attributes::instrument proc macro (as recommended in #12050), rust-analyzer won't expand that macro for me again.
The expansion buffer just shows the same function without the proc-macro attribute.
e.g.
#[tracing::instrument]fninstrumented(s:String){println!("Use s here: {}", s);}
With the proc-macro ignored, goToReferences on s works, but the expanded buffer contains the following:
// Recursive expansion of instrument! macro// =========================================fninstrumented(s:String){println!("Use s here: {}", s);}
Yeah that's what I expected, but in my mind as a user, telling RA to ignore a macro during code analysis does not necessarily mean that I don't want it to help me view what the macro expansion looks like
I absolute don't need this changed, I just wanted to bring it up :)
If I improve goToReferences on function arguments by ignoring the
tracing-attributes::instrument
proc macro (as recommended in #12050), rust-analyzer won't expand that macro for me again.The expansion buffer just shows the same function without the proc-macro attribute.
e.g.
With the proc-macro ignored, goToReferences on
s
works, but the expanded buffer contains the following:rust-analyzer version: rust-analyzer version: 0.3.1418-standalone (4e29820 2023-02-26)
rustc version: rustc 1.66.1 (90743e729 2023-01-10)
relevant settings:
The text was updated successfully, but these errors were encountered: