fix(scanner): Track Rust embedded file dependencies - #142
Conversation
Resolve literal include_str! and include_bytes! targets through the configured exact-file index while preserving conservative include! behavior. Co-Authored-By: GPT-5.6 Sol <codex@openai.com>
|
Reviewed in depth (adversarial pass with end-to-end probes on the PR head). The rule scoping is solid — 1. BLOCKING — phantom edge: the resolver's uniqueness check accepts extension-stripped index keys
Fix is the idiom your own sibling functions already use ( 2. BLOCKING —
|
Complied
Not fully complied
|
What does this PR do?
Record dependencies from literal Rust
include_str!andinclude_bytes!calls. Resolve relative paths only when the exact target is uniquely indexed in the repository; leave dynamic, missing, external, excluded, ambiguous, self, andinclude!targets unresolved.Type of change
Verification
go vet ./...go test ./...