Issues

Add Perl language support (.pl, .pm, .t) — grammar available, package scoping needs care

#1738

· netbrah opened

on Sep 7, 2026

Kotlin, Go, Rust: a private / unexported / non-pub definition is accepted as a cross-file name-match target

#1731

· danusha2345 opened

on Sep 7, 2026

C: a call resolves by exact name onto a static function in another translation unit (4,448 edges on betaflight)

#1730

· danusha2345 opened

on Sep 7, 2026

C: a macro call with designated-initializer arguments and a trailing comma runs the enclosing function to end of file, nesting or dropping every function after it

#1729

· danusha2345 opened

on Sep 7, 2026

Watcher scope diverges from indexer scope (.git/info/exclude, nested .gitignore) and every file event forces a full-project reconcile — 174k handles, 1.5-142s per single-file sync

#1728

· daragao3 opened

on Sep 7, 2026

C++: pure virtual methods get no node, so calls through an abstract interface don't resolve

#1727

· Dshuishui opened

on Sep 7, 2026

Export status is answered in three places, two of them hand-mirrored regexes

#1721

· bompus opened

on Sep 6, 2026

An import of a workspace package resolves onto a non-exported local variable of the same name (157 edges in vitejs/vite)

#1719

· bompus opened

on Sep 6, 2026

A bare call resolves onto the enclosing method when a same-file function shares its name

#1714

· bompus opened

on Sep 6, 2026

codegraph_explore: a trimmed file's elided symbols are never named, so the payload silently drops the answer and the footer's advice is circular

#1711

· bompus opened

on Sep 6, 2026

matchFuzzy resolves onto a nested function that matchByExactName had already rejected as lexically unreachable

#1708

· bompus opened

on Sep 5, 2026

TS/JS: a call through a chained receiver (chrome.storage.local.get, this.map.get, a.b.text()) reaches the resolver as the bare method name and exact-matches any project symbol with that name

#1707

· bompus opened

on Sep 5, 2026

Navigation Menu

All issues

Add Perl language support (.pl, .pm, .t) — grammar available, package scoping needs care

Kotlin, Go, Rust: a private / unexported / non-pub definition is accepted as a cross-file name-match target

C: a call resolves by exact name onto a static function in another translation unit (4,448 edges on betaflight)

C: a macro call with designated-initializer arguments and a trailing comma runs the enclosing function to end of file, nesting or dropping every function after it

Watcher scope diverges from indexer scope (.git/info/exclude, nested .gitignore) and every file event forces a full-project reconcile — 174k handles, 1.5-142s per single-file sync

C++: pure virtual methods get no node, so calls through an abstract interface don't resolve

Export status is answered in three places, two of them hand-mirrored regexes

An import of a workspace package resolves onto a non-exported local variable of the same name (157 edges in vitejs/vite)

A bare call resolves onto the enclosing method when a same-file function shares its name

codegraph_explore: a trimmed file's elided symbols are never named, so the payload silently drops the answer and the footer's advice is circular

matchFuzzy resolves onto a nested function that matchByExactName had already rejected as lexically unreachable

TS/JS: a call through a chained receiver (chrome.storage.local.get, this.map.get, a.b.text()) reaches the resolver as the bare method name and exact-matches any project symbol with that name

Search results