Add compiled-language extraction coverage#56
Merged
Merged
Conversation
Expand c, cpp, java, rust, and go to full query coverage with extraction cases, inline tests, and sample projects. Add SQL dialect fixtures (postgres, mysql, sqlite, duckdb, clickhouse) documenting how the single generic grammar parses each.
This was referenced Jul 2, 2026
Merged
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Close construct-coverage gaps for c, cpp, java, rust, and go, and add SQL
dialect fixtures.
The per-language capture sets grew organically and were never audited, so
definition-like constructs were invisible to search, navigation, and edges —
Rust
trait, Javainterface/enum/record, Cunion, C++namespaceandin-class methods. This is the systematic pass for the five compiled languages:
each gets its expanded query, extraction cases, inline tests, and a sample
project whose snapshot exercises the new constructs.
It also adds the five SQL dialect fixtures (postgres, mysql, sqlite, duckdb,
clickhouse). rbtr uses one generic
tree-sitter-sqlgrammar rather thanrouting
.sqlfiles to per-dialect grammars — routing is unreliable because afile carries no dialect marker, and the generic grammar recovers locally past
constructs it doesn't know. The fixtures document what that grammar extracts
per dialect, and each carries a strict-xfail parse-clean canary that will flip
if an upstream grammar bump starts parsing a dialect fully.
Stacked PRs (merge bottom → top): #54 · #55 · #56 · #57 · #58 · #59 · #60