You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 5a3e825
Browse filesBrowse the repository at this point in the historyBrowse files
fix(registry): gate C# type-keyword receiver check to CBM_LANG_CSHARP
The #2121 fix treated C#'s reserved type keywords (int, string, object,
...) as value roots in receiver_chain_admits without checking the
calling file's language. In Python, JS or Go those same spellings are
ordinary identifiers, so a lower-case variable named object or string
calling a method would fall through to the chain-consistency check and
could drop a real CALLS edge outside C#.
Add cbm_registry_resolve_lang(..., is_csharp) alongside the existing
language-blind cbm_registry_resolve, and thread is_csharp from each
file's own language at every call site that resolves a real receiver
chain: pass_calls.c and pass_parallel.c (the sequential/parallel CALLS
resolvers named in review), plus pass_semantic.c and pass_usages.c so
INHERITS/DECORATES/THROWS/RW edges stay gated the same way rather than
silently reverting to the pre-#2121 language-blind behavior. The two
remaining language-blind callers (pass_calls.c's Python-only Depends
scan, pass_lsp_cross.c's base-QN resolve which already excludes C#)
are documented in place as never reaching a C# receiver chain.
Adds a negative control test asserting a lower-case object/string
receiver root still resolves as a value in a non-C# file, pinning the
side of the gate a widened keyword list could quietly cost.
Signed-off-by: Amir Fathi <[email protected]>
0 commit comments