fix(rust): separate macro, value and associated call candidates #404
No reviewers
Labels
No labels
code-review
correctness
dos
performance
security
severity/high
severity/low
severity/medium
tech-debt
Kind/Breaking
Kind/Bug
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Security
Kind/Testing
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Won't Fix
Status
Abandoned
Status
Blocked
Status
Need More Info
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
h-dv/code-index!404
Loading…
Reference in a new issue
No description provided.
Delete branch "codex/rust-call-shapes"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Rust macro invocations such as
panic!()could appear as callers of an unrelatedfn panic, while bare and module-path calls competed with associated members. Local closure calls and match-guard callbacks could also bind to a same-named declaration elsewhere. This change carries the syntactic call shape from the owned Rust plugin through the validated interface into resolution and name fallback.The generic runtime admits three mutually exclusive fact-ABI 1.4 roles: macro, non-member value and qualified path calls. The Rust 0.1.5 plugin emits them and requests the existing
lexical_localcapability for proven local lookups. It requires runtime 0.41.6; existing approvals need an explicit grant of the new capability. Older packages keep their existing behavior. No language-specific parser enters the production runtime, and the frozen native Rust walker stays byte-identical.Validation includes:
[0,1,0,1,0]; every builtin pin refused.The source-reviewed Rust corpus binding audit records 87 gains, four corrected targets and 86 removals. Of the removals, 56 were false bindings. The other 30 were correct indexed-receiver calls (
ms[0]/msgs[n]) whose element types the runtime cannot prove. Their corrected method-call shape now leaves them unresolved under the existing receiver rule. This precision tradeoff is explicit; the change does not add speculative element-type inference. The pre-existing nested-owner path limitation also remains unresolved.Fixes #385.