rust-lang / rust-lang/rust-analyzer
Using `rust-analyzer.moveItem{Up,Down}` on `macro_rules!` removes `$capture_name` from macros args and body
Open
Nobody has claimed this yet.
C-bug
- Dominant language
- Rust
- Stars
- 16.9k
- Forks
- 2.2k
- Avg merge
- 1d 12h
- Merged PRs (30d)
- 72
Description
Before (| = cursor)
macro_rules! test {
($x:tt) => {
$x
};
}
|macro_rules! test2 {
($x:tt) => {
$x
};
}
rust-analyzer.moveItemUp
After (| = cursor)
|macro_rules! test2 {
(:tt) => {
};
}
macro_rules! test {
($x:tt) => {
$x
};
}
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the issue using rust-analyzer.moveItemUp with the two macro_rules! items shown, then inspect the move-item entry point and its handling of macro_rules! tokens. Done means moving the item preserves $capture_name in both the macro arguments and body, with the resulting code remaining valid.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100