rust-lang / rust-lang/rust-analyzer
Pretty error display like the one in the popular vscode extension pretty-typescript-errors
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 16.9k
- Forks
- 2.2k
- Avg merge
- 1d 12h
- Merged PRs (30d)
- 72
Description
Long error messages can be tricky and hard to understand at first glance
For example
the trait bound `poise::serenity_prelude::Timestamp: From<Result<poise::serenity_prelude::Timestamp, InvalidTimestamp>>` is not satisfied
the following other types implement trait `From<T>`:
`poise::serenity_prelude::Timestamp` implements `From<&poise::serenity_prelude::Timestamp>`
`poise::serenity_prelude::Timestamp` implements `From<DateTime<Tz>>`
required for `Result<poise::serenity_prelude::Timestamp, InvalidTimestamp>` to implement `Into<poise::serenity_prelude::Timestamp>`
I think it'd be better if we could display this error in a prettier format like in the vscode extension
https://marketplace.visualstudio.com/items?itemName=yoavbls.pretty-ts-errors
So instead we could have something like the full compiler diagnostics referenced inline, or something like
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
The issue names no files, tests, or entry points. Start by reviewing how rust-analyzer currently displays compiler diagnostics and compare that output with the linked pretty-typescript-errors example; done should mean a defined, agreed-upon prettier presentation for long diagnostics.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- devtools
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100