DEV Community

COMMENTERTHE9
COMMENTERTHE9

Posted on • Originally published at cx-lang.com

Cx Dev Log — 2026-05-16

The biggest concrete win today? Without a doubt, it was CX-218: a pivotal fix in lower_binary that took us from 8 arithmetic JIT parity passes, with 9 skips, to a much cleaner 13 passes and only 4 skips. This was no minor detail; it unblocked five more operations that had been silently sidestepping execution due to an unresolved type placeholder. Beyond that, the day was driven by determinism test coverage enhancements and some necessary site refinements.

The CX-218 Fix: Tackling SemanticType::Numeric in lower_binary

Whenever the lowering pass reaches an arithmetic expression—think 0 + 0 or 3 * 4—the result was defaulting to SemanticType::Numeric. This placeholder essentially waved a red flag, screaming "numeric type unresolved," until a fix could be devised. Previously, lower_value quietly resolved this to the target’s numeric_literal_ir_type(), defaulting to I64 on 64-bit systems. But lower_binary? Not so much. It was busy calling lower_type(result_ty), which cheerfully replied with UnsupportedSemanticType. Consequently, every test silently exited with a skip, leaving parity untested and unnoticed.

What changed? The fix mirrored lower_value by resolving SemanticType::Numeric directly to ctx.target.numeric_literal_ir_type() within lower_binary. A pragmatic move, even if it slightly duplicated logic across paths. If this tweak sounds like a band-aid, that's because it is. Until a centralized resolution emerges, this approach lets tests run and ensures zero parity failures.

Determinism Test Effort

Eight new PRs have made their way into submain. They are all gradually paving the way for our Phase 12 differential harness strategy, ensuring we remain on the cutting edge of determinism:

  • CX-197 (PR #238) — Improved determinism coverage.
  • CX-199 (PR #240) — Rebased CompoundAssign determinism tests.
  • CX-200 (PR #241) — Unary determinism tests, also rebased and fresh.
  • CX-202 (PR #243) — CodeRabbit’s logical OR fix freshens up CX-198.
  • CX-203 (PR #244) — While-in loop determinism tests, rebased cleanly.
  • CX-204 (PR #245) — Conditional branch merge patterns got some love.
  • CX-213 (PR #255) — Added documentation coverage following submain’s latest changes.
  • CX-214 (PR #256) — Determinism tests that cover complex pointer/array/casts for good measure.

These PRs showcase our revised strategy: each JIT instruction domain now demands a solid determinism test pass prior to implementation being folded into submain. The latest batch covered a broad array of operations: conditional branches, loops, various operators, and data constructs. Everything’s rebased, ready to merge, and straining at the leash, poised to boost our reliability matrix.

The Growing Submain Gap

Submain's pace has outstripped main by 164 commits, skyrocketing from just 40 a week ago. Main’s been sluggish, only seeing daily log updates, and its test matrix stands at 111 passes with a few notable failures. These are usually down to Result/try semantics and looping within functions. Submain, by all indications, clears all 117 tests currently identified. With such a divergence, integration's gonna be one tough cookie: an issue we’ve anticipated for a while, but no signs of a merge plan clear the horizon.

Elevating the Site

In a single day, five new commits polished the site to a gleam:

  • Documentation overhaul, aligned with the most recent interpreter/JIT operations, encompassing arrays, control-flow, and more.
  • Updated homepage status and voice, to reflect current capabilities.
  • Addressed mobile accessibility and fonts to improve user experience.
  • SEO and social metadata enhancements to prime us for public eyes.
  • Concise copy voice to round it all off.

This was no small feat. Aligning the docs with real Cx functionality (as opposed to past aspirational goals) was a massive step. Meanwhile, the SEO and accessibility tweaks hint that we’re getting ready for prime time.

What's Next

First up: push through the merges for CX-215 to CX-222 in submain. Eyes are particularly on CX-218 for its tangible code fixes, while the others bring in valuable determinism tests. The coming cycles promise more of the same: decisive determinism tests coupled with solid implementation once they pass muster.

But what of the submain-to-main merge? With a daunting 164 commits to reconcile, it looms large as our biggest conundrum. The site, freshly polished, seems to stand ready for its debut, assuming it's not waiting on the main branch to catch up. The path forward? Clear in parts but tantalizingly opaque in others.


Follow the Cx language project:

Originally published at https://cx-lang.com/blog/2026-05-16

Top comments (0)