rust-lang / rust-lang/rust-analyzer

Are we filling up hard drives with copies of the proc macro DLLs?

Open
#11,366 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

A-macro
Dominant language
Rust
Stars
16.9k
Forks
2.2k
Avg merge
1d 12h
Merged PRs (30d)
72

Description

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the linked rust-analyzer pull request #11365 and the intellij-rust issue #8139, since this issue names no files or tests. Determine whether proc macro DLL copies accumulate on disk, then document the affected path and provide a reproducible basis for a fix or follow-up.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
devtools
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.