fix(vbnet): link enum members with case_of instead of contains - #4054
rajatnagda45 wants to merge 1 commit into
Conversation
|
Thanks for the pull request, @rajatnagda45. A maintainer will review it soon. Want to talk it through while it is in review? Come join us on our Discord server. For longer-form discussion there is also GitHub Discussions. A couple of things that speed up review: make sure the test suite passes on Python 3.10 and 3.13, and that the change keeps extraction deterministic. |
There was a problem hiding this comment.
Graphify reviewed this change.
Looks safe to merge — no coupling regressions and no blocking issues, checked against the code graph (not a self-assessment).
Formal verification. PR-changed functions: 1/1 verified (0 proven, 1 may-equivalent, 0 distinguished) · 0 not verified.
Graphify review — findings
Fixes VB.NET enum members to hang off their enum via a case_of edge instead of contains, matching Java, C#, Swift and Scala. Because case_of targets are excluded from New X() constructor binding, an enum member named like a type no longer resolves as one. add_data_member now takes a relation argument, and class fields keep the default contains.
No blocking issues surfaced. 1 lower-confidence candidate did not survive cross-model review.
Analysis details — impact, health, verification
Impact & health
Graphify review
Impact — 23 functions depend on the 23 functions this change touches.
Health — this change adds coupling hotspots:
- new:
extract_vbnet()— 2 callers, 6 callees - new:
process_type()— 1 callers, 6 callees
Verification — 23 functions in the blast radius were not formally verified this run (proofs are advisory here).
Gate & verification
graphify gate
PASS — objectively clean (no health regressions, tests not run — proofs not run this pass (advisory)). Grounded, not self-assessed.
Advisory (not blocking):
- verification_scope: 23 function(s) in the blast radius were not formally verified this run
Test selection
Test selection
326 of 326 test file(s) selected (100%) via static blast radius.
Escalated to a full run for safety — the selection is not trustworthy on its own (see below). CI should run the whole suite.
tests/test_affected_cli.py— full-run-safetytests/test_affected_member_seed.py— full-run-safetytests/test_agents_platform.py— full-run-safetytests/test_analyze.py— full-run-safetytests/test_anthropic_custom_endpoint.py— full-run-safetytests/test_antigravity_install.py— full-run-safetytests/test_apm_fallback_version.py— full-run-safetytests/test_architecture_doc.py— full-run-safetytests/test_astro_extraction.py— full-run-safetytests/test_astro_import_ids.py— full-run-safetytests/test_atomic_canvas_export.py— full-run-safetytests/test_atomic_version_stamp.py— full-run-safetytests/test_atomic_writes.py— full-run-safetytests/test_backend_env_isolation.py— full-run-safetytests/test_backend_extras.py— full-run-safetytests/test_benchmark.py— full-run-safetytests/test_benchmark_raw_graph.py— full-run-safetytests/test_blade_extractor.py— full-run-safetytests/test_build.py— full-run-safetytests/test_build_merge_dedup_scope.py— full-run-safetytests/test_build_merge_hyperedges_and_prune.py— full-run-safetytests/test_build_merge_shrink_guard.py— full-run-safetytests/test_builtin_global_type_refs.py— full-run-safetytests/test_cache.py— full-run-safetytests/test_callflow_html.py— full-run-safetytests/test_cargo_introspect.py— full-run-safetytests/test_cargo_missing_manifest.py— full-run-safetytests/test_carried_hyperedge_remap.py— full-run-safetytests/test_case_sensitive_resolution.py— full-run-safetytests/test_charmap_encoding.py— full-run-safetytests/test_chunking.py— full-run-safetytests/test_cjs_module_extension.py— full-run-safetytests/test_claude_cli_backend.py— full-run-safetytests/test_claude_md.py— full-run-safetytests/test_cli_broken_pipe.py— full-run-safetytests/test_cli_export.py— full-run-safetytests/test_cli_help.py— full-run-safetytests/test_cluster.py— full-run-safetytests/test_cluster_exclude_hubs.py— full-run-safetytests/test_cobol_extractor.py— full-run-safetytests/test_codebuddy.py— full-run-safetytests/test_community_hub_labels.py— full-run-safetytests/test_community_labels_skill.py— full-run-safetytests/test_confidence.py— full-run-safetytests/test_corrupt_graph_json.py— full-run-safetytests/test_cpp_method_declarations.py— full-run-safetytests/test_cpp_nested_and_cli.py— full-run-safetytests/test_cpp_objc_cross_file_calls.py— full-run-safetytests/test_cpp_preprocess.py— full-run-safetytests/test_cross_extension_reexport_self_cycle.py— full-run-safety- … and 276 more
changed code file(s) with no mapped test (
graphify/extractors/vbnet.py) — a coverage gap or a missing link — running the full suite rather than only the selected tests
Selection is safe under the controlled-regression assumption; always-run tests + a periodic full run are the backstops. Advisory — it never changes the check verdict.
Formal verification
No difference found (not proven): No behavior difference found in extract\_vbnet (not a proof).
The verifier ran both versions of extract\_vbnet on many inputs and saw identical behavior every time. Strong evidence the change is safe, but evidence, not a proof.
Guarantee: Empirical: differential testing (both versions run on many generated inputs). A divergence on an untested input remains possible, so this is 'no counterexample found', not 'proven equivalent'.
Note: An input the sampler did not try could still differ.
· 1 grounded finding(s) anchored inline below; 1 more finding(s) on lines outside this diff (see the check run).
| add_edge(type_id, member_id, relation, member) | ||
| return member_id | ||
|
|
||
| def process_type(block: Node, parent_id: str, namespace: str) -> None: |
There was a problem hiding this comment.
process_type()
fans out to 6 callees (efferent coupling).
Grounded coupling-delta finding (deterministic), not an LLM guess.
|
Shipped in v0.9.76 (live on PyPI as Closing as shipped. |
Closes #4053
Problem
A VB.NET enum's members hang off the enum with a
containsedge, while every other language with enums emitscase_of:Cause
enum_membernodes went through the sameadd_data_memberhelper as real class fields, which always emitscontains. VB.NET was the only language still doing this (Java #1719, C#, Swift, Scala, C++, Rust, Zig, PHP all usecase_of).Why it matters
The relation carries resolution semantics, not just a label.
case_ofanddefinestargets are excluded fromNew X()constructor binding (_member_nidsinextract.py); ascontains, a VB.NET enum member whose name matches a type could be mis-bound as that type's constructor.Fix
Give
add_data_memberan optionalrelationargument (defaultcontains) and passcase_offor theenum_memberpath only. Real class fields are untouched.Tests
Added
test_vbnet_enum_members_emit_case_of_not_contains: enum members getcase_of(and notcontains), while a real class field keepscontains(and notcase_of). Fails on currentv8, passes with the fix. Full suite: 6345 passed, 15 skipped.ruffandpyrightclean on the touched file.