Call::callee_id falls back to name dispatch for first-class functions

LIMIT-TYPE-CONSTRUCTION-001

callee_id is empty for methods, nested functions and first-class function calls, which fall back to name dispatch.

Lifecycle

known

Owner

metel-frontend

Scope

architecture/spec/type-construction.md#type-construction

Origin

ADR-0041, ADR-0042 (corroborated independently in both)

Review

revisit once #542 has a concrete consumer for the sealed-accessor work ADR-0042 ties this to

Affects · linked records

arch.resolution.requirement-1architecture requirement

arch.type-construction.requirement-2architecture requirement

limitationKnown limitations ↗

Limitation

Call::callee_id: Option<SymbolId> is only populated where construction can determine a concrete callee SymbolId — it is None for methods, nested/local functions, and a call through a first-class function value. ADR-0041 and ADR-0042 both name this directly as "the deferred first-class-function environment question," not a bug — confirmed still present in current source (typed_ast/mod.rs's own doc comments on callee_id).

Impact

This is a real, currently-live exception to the resolution-freeze invariant (arch.resolution.requirement-1) for exactly this call shape: a call through a first-class function value still resolves by a name-keyed fallback at the point callee_id is None, not by identity alone.

Affects

• arch.resolution.requirement-1
• arch.type-construction.requirement-2

Resolution

None yet. ADR-0042 ties full closure to "once #542 has a concrete consumer" for the related sealed-accessor work; no scheduled fix as of this writing.