Resolves Gitea #1. Realises the "P2 follow-up" called out in
examples/prelude.ail line 9. Approach A (single-iter atomic
milestone): one cohesive cut across seven layers in one iter,
plus the regenerated prelude module hash pin.
Three design forks resolved with the user via brainstorm Q&A:
(1) Operator-name surface: `==` `!=` `<` `<=` `>` `>=` die from
the language. The LLM-author writes only the class-method
names `eq` `ne` `lt` `le` `gt` `ge` `compare`. One mental
model: AILang has class-dispatch, operators are not a
separate concept. Option 2 (keep names as surface aliases)
was rejected because it adds a second spelling for an
identical operation — the redundancy the milestone is
supposed to remove gets reintroduced syntactically. Option 3
(two-track: primitive Built-in for Int/Bool/Str/Unit, class
for user-types) was rejected because the two-pathy state is
precisely what this milestone exists to dismantle.
(2) Float comparison surface: Float keeps comparison capability
via six named prelude fns (`float_eq` `float_ne` `float_lt`
`float_le` `float_gt` `float_ge`), no `Eq Float` /
`Ord Float` instance. Motivation: all three feature-acceptance
clauses simultaneously satisfied — clause 1 (LLM-natural via
Library-Convention-Pattern like Python's `math.isclose` or
Rust's `approx`-crates), clause 2 (within the polymorphic
surface there is one path; Float is honestly stamped
"non-polymorphic"), clause 3 (the NaN-comparison anti-pattern
stays visible in code as `float_eq` rather than hiding
behind `eq`). Option A (Float loses all comparison) was
rejected as overstretch — workarounds via `is_nan` +
arithmetic are more bug-prone than a named fn that emits the
right fcmp directly. Option C (Eq Float with IEEE semantics)
was rejected as clause-3 violation — it would reintroduce
the silent NaN-comparison bug class that the existing
Float-no-Eq/Ord design exists to prevent.
(3) Codegen mechanism for primitive Eq/Ord instances: option β
(always-call through dispatch, with `alwaysinline` attribute
on intercept-emitted bodies as pre-emptive `-O0` mitigation,
and option α — call-site intercept — held as the bench-gate
fallback if measurements show real regression). Motivation:
semantic honesty (class methods ARE calls, optimiser folds
primitives uniformly at Int and User-Point alike), parity
with `Show` (which is also full-call today with no
intercept), smaller IR-shape contract for the existing pins.
Under `-O2` the inliner deterministically collapses 2-
instruction bodies; bench corpus runs `-O2`. Under `-O0`
`alwaysinline` overrides the no-inline default, giving the
same per-call IR shape as today. α was the initial-framed
Recommendation but was scrutinised in user pushback ("spricht
irgendwas FÜR β?") and after substantive re-balancing β
came out coherent.
Grounding-check (ailang-grounding-check) PASS on re-dispatch — 11
load-bearing assumptions ratified by:
`crates/ail/tests/e2e.rs::eq_demo` + `::lit_pat_demo`,
`crates/ail/tests/eq_ord_e2e.rs::eq_ord_polymorphic_runs_end_to_end`
+ `::eq_ord_user_adt_runs_end_to_end` + `::eq_ord_user_adt_eq_intbox_hash_stable`,
`crates/ail/tests/eq_float_noinstance.rs::eq_at_float_fires_float_aware_noinstance`,
`crates/ail/tests/prelude_free_fns.rs::ne_at_int_produces_mono_symbol` (+4 siblings),
`crates/ailang-surface/tests/prelude_module_hash_pin.rs::prelude_parse_yields_canonical_hash`,
plus in-source `#[cfg(test)] mod tests` ratifiers in
`crates/ailang-check/src/lib.rs` (`eq_typechecks_at_int/bool/str/unit`,
`mq2_env_method_to_candidate_classes_built`) and
`crates/ailang-codegen/src/lib.rs` (`lower_eq_str_calls_strcmp_with_bytes_pointer`).
The `alwaysinline` LLVM attribute is correctly classified as new
feature-work commitment (no live occurrences today), not as a
load-bearing assumption about present state.
First grounding-check pass BLOCKED on one spec defect — the spec
mischaracterised `crates/ailang-core/src/desugar.rs:2414` as "a
separate desugar pass" when it is in fact a `#[cfg(test)] mod tests`
AST-literal scaffold. Fixed inline: §Architecture and
§Components/4 now enumerate only `build_eq` (desugar.rs:1099) as
the sole production desugar site; `desugar.rs:2414`, `lib.rs:6092`,
`lib.rs:6220` are framed as test-scaffold migrations alongside the
production change, not as desugar-pass work. Re-dispatch PASS.
Out of scope (tracked separately):
- Deriving for Eq/Ord — `typeclasses.md:177` "No deriving"
stands; instance bodies remain hand-written.
- Parameterised-ADT instances (`instance Eq (List a)` etc.) —
requires constraint-propagation infrastructure, belongs to
Gitea #2 ("22c typeclass corpus expansion").
- Eq/Ord for the `Ordering` ADT itself — no use case; consumed
via match, not compared.
- `and` / `or` as Builtins — north-star fixture uses
`(if … … false)` for short-circuit conjunction; separate
concern.
refs #1
Brummel
a68d7b6353