rust-lang / rust-lang/rust-analyzer
Import code action for trait method only suggests to import alias
Open
Nobody has claimed this yet.
A-assists
C-bug
E-unknown
S-actionable
- Dominant language
- Rust
- Stars
- 16.9k
- Forks
- 2.2k
- Avg merge
- 1d 12h
- Merged PRs (30d)
- 72
Description
For example, for this code:
fn foo(res: std::io::Result<()>) -> eyre::Result<()> {
res.wrap_err("IO error")
}
there’s no code action to import eyre::WrapErr, only to import eyre::Context.
$ rust-analyzer --version
rust-analyzer 2022-04-11
$ rustc --version
rustc 1.60.0 (7737e0b5c 2022-04-04)
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
Start by reproducing the Rust example with rust-analyzer and inspect the code-action logic for trait-method imports. Done means the action suggests importing eyre::WrapErr, not only its Context alias, for the res.wrap_err call.
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
- 38/100