Two days of silence in the commit history—hardly ideal when submain is still fourteen days unmerged and a growing backlog of daily-log branches are knocking. The working tree on main is untouched, but submain? That's a different story.
The Submain Gap
Let's talk about submain. It's 14 days out, ahead of main with five crucial commits:
-
d93582b— shifts integer operations from saturating to wrapping, managing those trickyi128::MINedge cases. -
0fa06a6— drops Phase 10 enhancements in looping constructs with a fresh CFG structure, loop-carried SSA, and a backedge. -
09ef2a3— cements our stance on UTF-8, calling for strict adherence across the board. -
e214d15— specifies that semicolons are optional except in expression statements. -
762b188— initiates our basic test runner with assertions and a--testmode.
The diff against main is comprehensive: 24 modified files, with 367 lines added and 501 removed. Key files like main.rs, runtime.rs, parser.rs, and others reflect these tested changes. They address hard blockers in integer overflow, test running, and semicolon rules, alongside finalizing the UTF-8 decision. Yet, none of this has transitioned to main.
The only probable conflict? docs/frontend/ROADMAP.md, a shared edit site. But within the code, it's smooth sailing so far.
Daily-log Backlog
Today, that backlog hit nine, with new entries since yesterday. We have daily-log-2026-03-29 and a continuous stretch from daily-log-2026-04-01 through daily-log-2026-04-08. Each branch is a window into daily activities and plans—and a potential headache the longer they're delayed. Letting it pile up only raises the stakes for eventual merges, particularly with roadmap conflicts looming.
Roadmap Standoff
The roadmap holds steady at v4.8, still accurately mapping main's landscape. None of the hard blocker boxes—for the test runner, integer overflow, or semicolons—is checked, since the work isn't visible to main. The UTF-8 blocker is the exception, duly noted as a decision residing on submain. Any updates reflecting this work on main? Not happening yet; it'd be premature until merges land.
A quick navigation tip: roadmap instructions mistakenly refer to docment/ROADMAP.md. It's docs/frontend/ROADMAP.md.
What Lies Ahead
The plan is unbudged:
-
Submain to Main Merge. Front and center for 14 days: incorporate
submain's five commits and untangle any roadmap fallout. - Tackle the Backlog. Nine branches of daily logs wait to be unraveled, starting from the oldest.
-
Error Model (
Result). Syntax is defined in the spec, but there's no implementational trace yet. This becomes the pivotal blocker post-merge. -
:=Type Inference. Not started but much anticipated for 0.1.
The tempo's been idle, but the clock is ticking on these merges. Until submain graduates to main, we're stuck watching everything else stack up.
Follow the Cx language project:
- Website: cx-lang.com
- GitHub: github.com/COMMENTERTHE9/Cx_lang
- Dev.to: dev.to/commenterthe9
- Bluesky: thecomment.bsky.social
- Twitter/X: @commenterthe9
Originally published at https://cx-lang.com/blog/2026-04-09
Top comments (0)