Cx Dev Log — 2026-04-05

Source: Dev.to

Overview

Merging branches isn’t usually the most thrilling part of a project, but it’s crucial for keeping the bigger picture in sync. Today I focused on branch housekeeping for Cx, merging daily‑log PRs into main. The submain branch has been idle for ten consecutive days, holding key changes that haven’t yet gone live.

Merges to main

• PR #28 – added the 2026‑03‑28 daily log and bumped the roadmap to v4.8.

  • Annotations for Phase 8 ABI
  • Arithmetic enforcement
  • Phase 10 updates on while‑loop lowering

• PR #30 – merged the 2026‑03‑30 daily log into main.

The core of the project (compiler and runtime) remains stable at 78/78 on main.

Site Branch Updates

• Committed a 2026‑04‑04 blog post covering changes to the test runner and the Result design.
• Synced the 2026‑03‑29 branch with main; it’s a strong candidate for the next merge.

submain Branch Status

The submain branch holds five commits spanning eight days of work that have not yet landed on main:

These commits resolve four significant blockers (test runner, UTF‑8, integer overflow, and semicolons) and pass all tests on submain with a score of 82/82, while main remains at 78/78. Despite the readiness, the merge has not occurred for over a week.

Pending Daily‑Log Branches

Five daily‑log branches are still waiting to be merged:

• 2026‑03‑29 (now synced and ready)
• 2026‑04‑01
• 2026‑04‑02
• 2026‑04‑03
• 2026‑04‑04

If left unattended, these branches could introduce divergent roadmap versions and cause cumulative conflicts in docs/frontend/ROADMAP.md.

Current Roadmap (v4.8)

The roadmap reflects only what has officially landed on main. The work on submain is unacknowledged on paper, making the roadmap appear conservative.

Priorities

1. Merge submain into main – five important commits, four blockers resolved. This has been the top action for over a week.
2. Clear the daily‑log branches – prevents roadmap conflicts and backlog buildup.
3. Finish the error model (Result) – a hard blocker after the test runner work; detailed in yesterday’s blog post.
4. Kick off type inference – listed but awaiting initiation.

Project Status

The project is in an unusual state: crucial, validated work resides in submain, but it remains unmerged. Until this bottleneck clears, downstream efforts (error model, backend work) cannot progress beyond speculation.

Follow the Cx Language Project

• Website:
• GitHub:
• Dev.to:
• Bluesky:
• Twitter/X: @commenterthe9

*Originally published at *