RFC-0040 · Design Q&A
Versioned draft snapshot
RFCs, reference catalogs, and evidence reflect Spec 3b2e3e7a114fb826b1445d39a48756b8fff629cd. Counts and pending/status notes belong to that snapshot. Read the dated project update for later progress.
Source repositories are private during staging. Links marked “repository access required” need access to the linked repository.
Q: How are unqualified template imports resolved when multiple dependencies export the same name?
Status: Open
Source: RFC-0040 §§4.1–4.2, 10; RFC-0039 §4.3
Issue: templates: examples use bare names resolved against the full dependency closure, while calls use module aliases. The RFC does not define collision precedence, whether transitive re-exports are candidates, or how the declared import is matched to a qualified call.
Recommendation: Require a qualified module alias or define an explicit ambiguity diagnostic and deterministic resolution procedure; make the access-control check operate on the resolved identity.
Q: Can a re-export-only aggregate module have an empty objects map?
Status: Open
Source: RFC-0040 §§3.1, 4.3, 9, 12 invariant 2
Issue: The RFC preserves aggregate modules that re-export imported modules, but objects must contain at least one entry. A module that only re-exports dependencies is rejected even though no local object is needed.
Recommendation: Permit an empty object map when the manifest has a nonempty export surface, or explicitly require and define a meaningful local aggregate declaration.
Q: Which sources determine the reproducible manifest hash?
Status: Open
Source: RFC-0040 §§8, 9.6, 11, 12 invariant 10 Issue: The pipeline reads transform inputs and file-path objects before hashing, but the RFC does not say whether the hash covers their bytes, parsed content, resolved dependencies, compiler version, or transform profile. The same manifest text can therefore compile differently without changing its hash. Recommendation: Specify canonical hash inputs, including all loaded and generated content and pinned dependency identities, and define normalization and compiler-version behavior.
Q: Which install options may be fixed inside a published module manifest?
Status: Open
Source: RFC-0040 §§6, 11; RFC-0041
Issue: defaultConfig includes forceReinstall and skipOptionalDependencies, which are operational install controls. A published module can thereby request its own reinstall or omit dependencies, but precedence against installer policy and lockfile resolution is not defined.
Recommendation: Separate declarative module defaults from installer invocation options, or define explicit precedence and admissibility checks for each operational flag.
Q: Is the compile pipeline allowed to consume dependency declarations during transforms?
Status: Open
Source: RFC-0040 §§4, 8, 11 Issue: Transforms run before dependency closure resolution, yet generated objects can need imported types and templates. The RFC does not define whether transforms may inspect dependencies, how generated imports are validated, or whether transform output can alter the dependency set. Recommendation: Specify a two-stage compile: parse and lock dependencies, run deterministic transforms against that locked context, then validate generated objects and reject dependency changes.