Allow SCIP to contribute symbols for unsupported languages
- Dominant language
- C++
- Stars
- 2.1k
- Forks
- 125
- Avg merge
- 5h 42m
- Merged PRs (30d)
- 136
Description
Ripwire currently uses SCIP as a precision overlay over symbols already extracted by its built-in grammars.
Would you consider an opt-in mode allowing a SCIP index to contribute definitions and references for files whose language is not natively supported?
This would support proprietary and legacy-language frontends without runtime grammar loading or additional dependencies. The default path would remain byte-identical, deterministic and unchanged when the option is absent.
If this fits Ripwire’s architecture, I would be interested in preparing a small, gate-first implementation.
Contributor guide
Research direction
Start by tracing Ripwire's existing SCIP integration and built-in language-support path; the issue does not name specific files or tests. Define how an opt-in gate would let SCIP provide definitions and references for unsupported languages while preserving the absent-option path byte-identically and deterministically, then identify the relevant validation coverage.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- cli, devtools
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 45/100