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 c933d0b
Browse filesBrowse the repository at this point in the historyBrowse files
fix(pipeline): a bare C reference never binds a struct Field
A bare C identifier that names no visible declaration reached the
short-name registry fallback in the USAGE and READS/WRITES resolvers,
which bound it to whichever struct member carried the same name.
tests/test_main.c's RUN_SELECTED_SUITE(mcp) gave `main` a USAGE edge
to cbm_daemon_application_session.mcp, and every bare local write
(`offset = 0`, `trait_qn = head`) became a WRITES edge to an unrelated
struct's field.
In C a member is only ever named as the member half of `a.b`, `a->b`
or a designator `.b`, all recorded as is_member_access and bound
through the C LSP owner rows. Widen the Go rule (DeusData#1942/DeusData#1962) to C:
cbm_go_suppress_bare_field_ref becomes cbm_suppress_bare_field_ref and
takes the caller language. C++ (and every .h, parsed as C++) keeps its
bare member references, as a method body names its own members
without a selector. Sequential and parallel resolvers both consult it.
FixesDeusData#2666
Signed-off-by: Gaurav Dubey <gauravdubey0107@gmail.com>
0 commit comments