rust-lang / rust-lang/rust-analyzer
Diagnose unbalanced delimiters
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 16.9k
- Forks
- 2.2k
- Avg merge
- 1d 12h
- Merged PRs (30d)
- 72
Description
Rust has great diagnostics for unbalanced delimiters, it is shame r-a has NOTHING for them at all. We should fix that, it is invaluable to immediately see the problem when typing, copying or refactoring introduce unbalanced delims.
For:
(
(
[
)
)
rustc produces
Compiling playground v0.0.1 (/playground)
error: mismatched closing delimiter: `)`
--> src/main.rs:4:9
|
3 | (
| - closing delimiter possibly meant for this
4 | [
| ^ unclosed delimiter
5 |
6 | )
| ^ mismatched closing delimiter
error: could not compile `playground` (bin "playground") due to previous error
meanwhile r-a just screams:
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 unbalanced-delimiter example in rust-analyzer and compare its diagnostics with the rustc output shown in the issue. Trace the diagnostic path for malformed delimiter nesting, then identify the relevant tests or entry points; done means the example reports the unclosed and mismatched delimiters with useful locations.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- compilers
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100