gnomonlearn
Docs/RFC-0021/Design Q&A

RFC-0021 · 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.

← Read the authored RFC

The cross-RFC contract and diagnostic migration proposal is in TEL_CONTRACT_PROPOSAL.md. Its recommendations remain proposals until the authored RFCs and generated catalogs are reconciled.

Q: Can a transform with a potentially zero denominator compile successfully?

Status: Open

Source: RFC-0021 §2 goal 1; §6.3; §9 invariant 1; M21114 Issue: The RFC requires every accepted transform to be total and produce a non-error value for every input, but §6.3 emits only a warning when the denominator may be zero and says execution will propagate an error value. Recommendation: Make an unproved nonzero denominator a compile error for the total TEL profile, or explicitly define a partial profile with a different contract. Do not call the warning-only profile total.

Q: Which grammar and binding are authoritative for migration transform expressions?

Status: Open

Source: RFC-0021 §1, §3, §9 invariant 3; RFC-0008 §6.32 and §11; RFC-0016 §2.4 Issue: RFC-0021 says TEL is a strict subset of RFC-0008 §11, but that section defines visibility and epistemic state, not an expression grammar. TEL binds input to one old field value, whereas RFC-0008’s declared migration transform uses an apply { field = expr } block and the source entity binding source. Recommendation: Define TEL as the field-expression subset used inside RFC-0008 §6.32 apply assignments, with an explicit mapping between input and the appropriate source field or a consistent source binding. Update the predecessor cross-references together.

Q: When do M21xxx diagnostics replace M01603 and M16021?

Status: Open

Source: RFC-0021 §7 and §9 invariant 5; RFC-0016 §2.4/§10; RFC-0008 §6.32 Issue: RFC-0021 narrows M01603 to an indeterminate language version after ratification, while RFC-0016 still assigns M01603 to any non-total referenced transform and RFC-0008 assigns M16021 to a non-total apply expression. The exact migration and compatibility period are unspecified. Recommendation: Publish a code-by-code migration table and update both predecessor RFCs before changing compiler output or diagnostic consumers.

Q: When will collection-typed field transforms be specified?

Status: Open

Source: RFC-0021 §1 and M21108 Issue: Collection operations are deliberately excluded because totality is harder to prove. No follow-up RFC or acceptance criterion is named.

Trigger: Assign a compiler-owned extension RFC before claiming collection transforms are supported.