diff --git a/docs/language_status/c.md b/docs/language_status/c.md index 265f3cffe..2db899bb9 100644 --- a/docs/language_status/c.md +++ b/docs/language_status/c.md @@ -289,7 +289,9 @@ does not (6 occurrences) was individually read. **All 6 are inside `#if 0` dead (`sqlite/lemon.c:3443`, K&R-style *and* dead). tree-sitter-c has no preprocessor model and parses the dead branch; GitGalaxy correctly skips it (Claim 8). The accuracy audit was corrected to drop `#if 0` / `#if false` function definitions from ground truth — **C func recall 99.7% → -100.0%**, zero real recall gaps. +100.0%**, zero real recall gaps. The C `func_start` compiler-attribute shield also picked up the +same [#2460](https://github.com/squid-protocol/gitgalaxy/issues/2460) SAL / entry-point +annotation-macro prefix as C++ (for consistency; the C corpus does not currently exercise it). (found and fixed as part of the same pass) or a known tree-sitter-c/ctags limitation — never GitGalaxy's regex engine itself. Current measured numbers (`tests/tools/tri_comparison_chart.py --languages c`, `language-crucible/data/c/` — diff --git a/docs/language_status/cpp.md b/docs/language_status/cpp.md index d4b954e39..086824cb9 100644 --- a/docs/language_status/cpp.md +++ b/docs/language_status/cpp.md @@ -312,7 +312,10 @@ breakdown: tree-sitter has no preprocessor model (Claim 8). - **1 real GitGalaxy recall gap** — `__control_entrypoint(DllExport) STDAPI DllCanUnloadNow()` in `powertoys/ImageResizerExt.cpp`: a macro-supplied return type `func_start` doesn't admit. - → [#2460](https://github.com/squid-protocol/gitgalaxy/issues/2460). + → [#2460](https://github.com/squid-protocol/gitgalaxy/issues/2460). **Fixed** (2026-08-29): the + `func_start` compiler-attribute shield now also consumes a `__`- / `_Uppercase`-prefixed + SAL / entry-point annotation macro (naming-shape bounded so it can't eat a real call). Cpp func + recall 99.9% → 100.0%. Six real GitGalaxy engine defects were confirmed and filed in this sweep — more than any other language this sweep methodology has been run against so far, though that reflects C++'s syntactic diff --git a/docs/language_status/lua.md b/docs/language_status/lua.md index 16a470523..510700b30 100644 --- a/docs/language_status/lua.md +++ b/docs/language_status/lua.md @@ -60,11 +60,12 @@ tradeoff. ## 5. Known limitations (accepted / tracked) -- **Two recall misses** (skill step 2.6 recall audit, 2026-08-29 — func recall 99.7%), both - filed as [#2461](https://github.com/squid-protocol/gitgalaxy/issues/2461): - - `constructs.lua:105` — `local a; local function f(x) ... end`. `func_start` is - start-of-line anchored, so a `local function` that is not the first statement on its line is - missed. GitGalaxy finds the other 4 `function f` in the file; this is a real, narrow gap. +- **One residual recall miss** (skill step 2.6 recall audit, 2026-08-29 — func recall 99.7% → + **99.8%** after the fix below), filed as + [#2461](https://github.com/squid-protocol/gitgalaxy/issues/2461): + - `constructs.lua:105` — `local a; local function f(x) ... end`. **Fixed** (2026-08-29): + `func_start` / `function_opener` now also anchor after a bare `;` statement separator, not + only start-of-line. - `literals.lua:80` — `local function lexerror (s, err)`, inside `test/literals.lua` (the Lua suite's *lexer-torture fixture*, adversarial nested `[==[[===[[=[…]]=][====[…]` long brackets that defeat `_LUA_LONG_BRACKET_RE`'s single-backref shielding). Only ever exercised @@ -267,9 +268,10 @@ shared reason." This is the common case per the skill's step 4 guidance. heuristic matched ALL_CAPS data tables. - [#2440](https://github.com/squid-protocol/gitgalaxy/issues/2440) — **fixed**: polyglot segmentation split a function at `