Exact

Exact Union RegExp

Gergő Magyar 5fa73bafdf feat: Phase 4 type resolution — nullable unwrapping, for-loop typing, assignment chains, code review fixes (#310) ... * feat: Phase 4 type resolution — nullable unwrapping, for-loop typing, assignment chains, Kotlin return types Phase 4.1: Nullable/optional chain unwrapping - Add stripNullable utility in shared.ts for stripping nullable wrappers - Apply in lookupInEnv to unwrap User | null → User, User? → User before receiver lookup - Handles TS union, Kotlin/C#/Swift nullable suffix, Python Union[T, None], Rust Option<T> - Enables receiver-type disambiguation through ?. optional chaining Phase 4.2: For-loop element typing (Tier 0 — Java/C#/Kotlin) - Add ForLoopExtractor type and forLoopNodeTypes to LanguageTypeConfig - Java enhanced_for_statement, C# foreach_statement, Kotlin for_statement extractors - Only explicit element types in AST (Tier 0); inference-based languages deferred Phase 4.3: Assignment chain propagation (single-pass, depth-1) - Add PendingAssignmentExtractor to LanguageTypeConfig with per-language implementations - Handles TS/JS variable_declarator, Rust let_declaration, Python assignment, Go short_var_declaration, C# equals_value_clause, Java/Kotlin variable_declarator - Single post-walk propagation pass (no fixpoint iteration per Sorbet/Pyright design) - Resolves const b = a; b.save() when a has known type from Tier 0/1/1b Phase 4.5: Kotlin return type extraction (bug fix) - Fix extractMethodSignature to handle Kotlin user_type after function_value_parameters - Remove lenient test assertions, add strict disambiguation proof Integration tests across 10+ languages with competing same-name methods and negative assertions proving disambiguation. * fix: per-language assignment chain gaps from code review - Kotlin: new extractKotlinPendingAssignment for property_declaration → variable_declaration AST (Java's variable_declarator doesn't exist in Kotlin) - Go: handle var_spec (var b = u) alongside short_var_declaration (:=) - PHP: add extractPendingAssignment for $alias = $user with $ prefix preserved Integration tests added for all three languages with competing same-name methods and negative disambiguation assertions. * fix: code review fixes — DRY nullable keywords, avoid array allocations, clarify depth comment Addresses findings from 6-agent code review on PR #310: - Move stripNullable JSDoc to correct position (was orphaned above NULLABLE_KEYWORDS) - DRY: reuse NULLABLE_KEYWORDS set in pipe-split filter instead of inline strings - Replace node.children.find() with findChildByType/manual loops in jvm.ts, go.ts, csharp.ts to avoid unnecessary array allocations per tree-sitter call - Clarify "depth-1" comment in type-env.ts: single-pass resolves multi-hop chains when forward-declared; reverse-order is depth-1 only - Annotate extractGenericTypeArgs as Phase 5 infrastructure (zero production callers) - Re-export PendingAssignmentExtractor from index.ts for API consistency - Add explicit return undefined in Go extractPendingAssignment - Remove redundant child.text === '=' check in Kotlin extractor Test coverage: - 20 new unit tests: stripNullable edge cases, per-language assignment chains, reverse-order depth limitation, nullable lookup resolution - 15 new integration tests: multi-hop chains (a→b→c), nullable+chain combined (User|null + alias), Python User|None through stripNullable path - 3 new fixtures: ts-multi-hop-chain, ts-nullable-chain, python-nullable-chain * fix: third-pass review — walrus chain, scanner allocations, Kotlin variable_declaration, C# type guard Addresses 4 new findings from third-pass CI review: 1. Python walrus operator (:=) now handled by extractPendingAssignment — named_expression nodes propagate alias chains alongside regular assignment 2. Scanner .namedChildren.find()/.some() in jvm.ts replaced with findChildByType() — consistent with 98daed4 code review fixes 3. Kotlin extractPendingAssignment extended to handle variable_declaration nodes in addition to property_declaration (function-local val/var) 4. C# extractPendingAssignment early-returns for is_pattern_expression and field_declaration nodes (never contain variable_declarator children) Integration tests: - Python: walrus chain (alias := u) with disambiguation (5 tests, 1 fixture) - Kotlin: assignment chain with typed declarations (5 tests, 1 fixture) - C#: assignment chain + is-pattern coexistence (6 tests, 1 fixture) - Unit: Python walrus propagation (1 test) * feat: nullable wrapper unwrapping + C++ assignment chains Gaps 1, 2, 4 from code review — architectural changes to type resolution: 1. extractSimpleTypeName now unwraps nullable wrapper generics: - Optional<User> → "User" (Java), Option<User> → "User" (Rust), Maybe<User> → "User" (Kotlin Arrow/Haskell-style) - Containers (List, Map) and async wrappers (Promise, Future) are NOT unwrapped — methods are called on the container, not the inner type - Uses existing extractGenericTypeArgs (now production-active, was dead code) - NULLABLE_WRAPPER_TYPES set: Optional, Option, Maybe 2. C++ extractPendingAssignment added for auto alias chains: - auto alias = user; alias.save() now propagates User type - Handles pointer/reference declarators, auto/decltype(auto) 3. Updated existing Rust test: Option<User> parameter now correctly stores "User" instead of "Option" in TypeEnv Integration tests with fixtures for Java Optional, Rust Option, C++ auto chain. Full pipeline resolution marked .todo — requires call-processor enhancement (TypeEnv stores correct types but call-processor needs additional work to produce CALLS edges for these patterns). Unit tests: 196 passed (7 new). Integration: all 9 languages green. * fix: resolve .todo tests — stale dist/ was the root cause The Rust Option<User> and C++ auto assignment chain integration tests were marked .todo because the pipeline didn't produce CALLS edges. Root cause: dist/ was compiled from pre-Phase 4 source and lacked: - NULLABLE_WRAPPER_TYPES unwrapping in extractSimpleTypeName - C++ extractPendingAssignment After npm run build, all tests pass as real assertions: - Rust: alias.save() resolves to User#save via Option<User> unwrap + chain - C++: alias.save() and rAlias.save() resolve via auto assignment chain with correct disambiguation (User vs Repo) Only remaining .todo: Rust user.unwrap().save() (Phase 5 — chained return type inference, not a TypeEnv issue).		2026-03-16 15:21:54 +00:00
..
app.py	feat: Phase 4 type resolution — nullable unwrapping, for-loop typing, assignment chains, code review fixes (#310)	2026-03-16 15:21:54 +00:00
repo.py	feat: Phase 4 type resolution — nullable unwrapping, for-loop typing, assignment chains, code review fixes (#310)	2026-03-16 15:21:54 +00:00
user.py	feat: Phase 4 type resolution — nullable unwrapping, for-loop typing, assignment chains, code review fixes (#310)	2026-03-16 15:21:54 +00:00