rust-lang / rust-lang/rust-analyzer
Implement `SyntaxKind` support for our SCIP backend
Open
Nobody has claimed this yet.
A-lsif/scip
C-feature
- Dominant language
- Rust
- Stars
- 16.9k
- Forks
- 2.2k
- Avg merge
- 1d 12h
- Merged PRs (30d)
- 72
Description
- UnspecifiedSyntaxKind
- Comment
- PunctuationDelimiter
- PunctuationBracket
- Keyword
- IdentifierOperator
- Identifier
- IdentifierBuiltin
- IdentifierNull
- IdentifierConstant
- IdentifierMutableGlobal
- IdentifierParameter
- IdentifierLocal
- IdentifierShadowed
- IdentifierNamespace
- IdentifierFunction
- IdentifierFunctionDefinition
- IdentifierMacro
- IdentifierMacroDefinition
- IdentifierType
- IdentifierBuiltinType
- IdentifierAttribute
- RegexEscape
- RegexRepeated
- RegexWildcard
- RegexDelimiter
- RegexJoin
- StringLiteral
- StringLiteralEscape
- StringLiteralSpecial
- StringLiteralKey
- CharacterLiteral
- NumericLiteral
- BooleanLiteral
- Tag
- TagAttribute
- TagDelimiter
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 locating the SCIP backend entry point and the existing SyntaxKind definitions. Trace how syntax kinds are represented and reported, then use the checklist as the completion criteria: all listed kinds should have support. The issue names no files or tests, so the relevant validation path must be discovered first.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- devtools
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100