Field-wise Clone is unavailable for records imported from another module

LIMIT-TYPE-INFERENCE-012

A public nominal record imported from another module has no visible field-wise Clone method, even when every field is Clone.

Lifecycle

resolved

Owner

metel-frontend

Scope

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

Origin

v0.14.0 release-matrix probe; metel-core#1421

Affects · linked records

spec.declarations.records.legality-1language spec rule

spec.modules.imports.legality-2language spec rule

limitationKnown limitations ↗

Limitation

A public Packet record declared in one module with Clone fields was not recognized as Clone in a consumer module because the registry merge omitted its record-kind identity. The merge now carries that identity, and module_semantics/release_matrix_record_clone_cross_module passes without a skip. The fix merged in metel-core PR #1422.

Impact

Previously, field-wise record Clone could not be relied on across module boundaries, despite the public record and its Clone aspect being available.

Affects

• spec.declarations.records.legality-1
• spec.modules.imports.legality-2

Resolution

Implemented in metel-core commit 5f038b189cb67c5ec40e51d16a3e11a831a4535e (PR #1422), with the executable imported-record Clone fixture above as exit evidence for metel-core#1421.