Skip to content

Add Rust-owned C baseline extraction#677

Merged
jununfly merged 2 commits into
mainfrom
zjal/rust-owned-c-baseline
Jul 3, 2026
Merged

Add Rust-owned C baseline extraction#677
jununfly merged 2 commits into
mainfrom
zjal/rust-owned-c-baseline

Conversation

@jununfly

@jununfly jununfly commented Jul 3, 2026

Copy link
Copy Markdown
Owner

Summary

  • Add Rust-owned C baseline extraction for functions, structs, enums, enum members, typedefs, includes, calls, and variables.
  • Mark C as a rust-hybrid Rust-owned language and classify ambiguous .h files by content before assigning ownership.
  • Remove the migrated TypeScript-owned C extractor path while keeping the C++ TypeScript extractor.
  • Record cJSON real-corpus validation and update the Rust-owned migration roadmap.
  • Retain the ZAgenticLoop scaffold and closeout state per Human Gate decision.

Validation

  • cargo build --package zcodegraph-core
  • npm run build
  • npx vitest run __tests__/rust-index-engine-cli-language-smoke.test.ts __tests__/rust-index-engine-cli-fallback.test.ts __tests__/rust-index-engine-cli-engine.test.ts
  • npx vitest run __tests__/extraction.test.ts -t "C/C\\+\\+ imports|Objective-C|detect language"
  • git diff --check
  • Real corpus: DaveGamble/cJSON at fb16e5c, 121 indexed files, 3,581 nodes, 7,000 edges, engineByLanguage.c = rust, no Rust-owned C gap diagnostics.

Post-Merge

  • Delete branch zjal/rust-owned-c-baseline after merge.

@jununfly
jununfly merged commit a27a8b5 into main Jul 3, 2026
3 checks passed
@jununfly
jununfly deleted the zjal/rust-owned-c-baseline branch July 3, 2026 09:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant