Structs Phase 1+2 landed on submain with impl blocks, methods, and compound assignment through dot-access, plus a new verification matrix test runner.

Phase 11 lands compound assign lowering on submain, bringing +=, -=, *=, /=, and %%= into the IR backend with full SSA handling.

Phase 8 Round 1 landed scalar layout definitions and the first formal ABI design document for Cx.

This article emphasizes the importance of documenting Microsoft .NET code with XML documentation and code comments. It covers the purpose and benefits of XML documentation, setting up the project f…

v0.3.2 shipped with the complete gene/phen trait system, operator overloading via an embedded prelude, and a full submain-to-main merge.

A quiet day with no new compiler commits, while the submain-to-main integration and stalled example rewrites continue to wait.

ComponentSource has awarded SubMain a Top 100 Publisher Award in the annual ComponentSource Awards for 2026.

Day six of a development pause with 26 unmerged commits on submain covering monomorphization, call-depth guards, and const/exit lowering still waiting for merge.

The Stream and Wetlands Foundation told commissioners it holds conservation easements on parcels in the Ford Grove submain, said those parcels already provide stormwater retention, and urged the county to confirm Clean Water Act permitting before finalizing costs.

A quiet day on the Cx repo with no new commits, while submain sits 12 commits ahead of main waiting for merge.

Submain sits 12 commits ahead of main, ready for a merge that's been "most likely next" in every daily log for days. If you want to catch a project in a moment of tension, there's no better time. No commits added recently, but in the quiet lies the pushback of a pending decision. ## Current State Main holds strong at 380 passes and zero fails—a pristine test matrix. On its tail, submain checks in at 345 passes, zero fails, but with 51 skips across 396 test fixtures. Despite the skips, nothing's broken. As far as v0.3.2 goes, we're stable post-release after adding gene/phen support, operator overloading, and fixing the struct-return ABI. Not a single regression logged. ## The Submain Situation Let's talk about submain’s restless state, dangling those 12 commits. The work includes some key technical progress like exit and const lowering, a crucial parser guard fix, and a README accuracy pass. Moreover, there's a comprehensive audit pushing the C1-C4 enforcement layer to completion. We've got no visible merge conflicts. All that's missing is a green light for integration—tests are passing, the diff is clean, and yet, the commits remain stranded. Not a blocker in sight, just an unturned page in this project’s log. ## Open Issues Issues are stacking—#15 through #17—with tags since 07-27. These deal with constant-index out-of-bounds and division mishaps, runtime-checked string interpolation, and some diagnostic bugs. No hands have touched them so far. #16 might hold the path of least resistance, promising a cleaner follow-up by relocating validation to the analysis phase. Getting through these would clear some anxieties lying under the surface. ## What's Next The log keeps reiterating the same next steps, and they remain clear: 1. **Merge submain into main.** It's straightforward: zero conflicts, twelve commits, all tests clear. 2. **Tackle Issues #15-#17.** With #16 being most self-contained, it might deserve a start. 3. **Scope for 0.3.3.** Eyeing array-return lowering, generic-function lowering, and expression receivers for the future. All this while holding strong in a stable post-release calm. The merge of submain and the 0.3.3 scoping represent the next milestones. Making space for untangling those issues could set the stage for forward strides. **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-07-29_

v0.3.2 shipped with the complete gene/phen trait system, operator overloading via an embedded prelude, and a full submain-to-main merge.

Two substantial slices of gene/phen trait implementation just landed on `submain`. This shifts the needle significantly—contract checking and the capability for phen methods to actually get called at runtime are in the door. Previously, we only had the basic declarations and coherence working but now methods can type-check, `Self` can resolve per receiver, and calls execute. The `submain` branch now sits 15 commits ahead of `main`, holding the matrix at 321/0. ## Contract Checking and `Self` Resolution (Slice 2) Let's zero in on commit `fcd3193`, which makes waves with 594 insertions across 23 files. The big takeaway is Pass 0 contract conformance. The `collect_gene_phen_registry()` function now actively validates every phen against its gene. Consider everything from arity to positional parameter types (post-`Self` substitution), return types, and even checks for both missing and extra methods. If there's a mismatch, it doesn’t just shout—each one is a precise diagnostic identifying gene, method, position, and expected-vs-actual types. It's pinpoint troubleshooting. The decision to resolve `Self` at the concrete level before analysis was deliberate. `Self` in phen signatures and bodies changes to the actual receiver type within the AST thanks to `substitute_self_type()`. This function even navigates through intricate structures like `Array`, `Handle`, and `Result` wrappers. There was an alternative: treating `Self` as a floating type parameter. But honestly, it doesn't cut it because `types_compatible` would unify any type param with anything. Sticking to the design docs, our path—`Self` is concrete, not a floating parametric. How about ownership? It's strict. There's no room for unauthorized methods beyond the gene's contract. And we're talking multiple enforcement points: from Pass 0 checks to the `phen_methods` field on `Analyzer` triggered during per-file analysis, down to cross-gene-method name collisions caught by Pass 0. Every path specified is locked down, as envisioned by the design docs. `PhenDef`’s semantic representation beefed up. `SemanticStmt::PhenDef` now contains `Vec` and `Vec>` instead of just plain method names. Methods undergo scrutiny in temporary scopes just like their impl-block cousins. Testing isn’t left out. We've packed ten new negative test fixtures plus a positive one to exercise every rejection path—think contract arity mismatches, missing and mismatched methods, and more. The positive test? `t_gene_phen_contract_ok` checks two phens of a single gene with `Self` in all type positions, acting as a 'leak' canary. ## Phen Method Calls at Runtime (Slice 3) Switch to commit `cbb095e`. This is the one where phen methods get street-legal, callable status. The insight here: phen methods log into `semantic_impls` keyed on `(type_name, method_name)` with receiver bindings—the same data architecture impl-block methods leverage. Therefore, `call_semantic_method` dispatches phen calls without any tweaks, reaffirming the design doc where phen methods function as full-fledged implementations identical to an impl block's. Surprisingly, forward-reference support hitchhiked into the build. The pre-registration pass in `run_with_interpreter_setup()` slots in phen methods right alongside impl methods, seamlessly supporting forward-call breakouts. Picture it—textual call sites preceding phen declarations still dispatch accurately. Six new test fixtures? You bet. We cover the gamut from basic construct-call-use-return pathways to multi-type dispatch and forward references. We didn’t overlook parity for phen versus impl methods in mutation scenarios, or `Self` typed params and returns in execution. ## Design Decisions Confirmed These slices pivot around the established design doc rather than veering off in new directions: * `Self` being concrete, not parametric, echoes decision 3. The `t_gene_phen_self_leak_reject` fixture underscores this—annotating an Enemy literal as `Self` in a Player phen remains a type error. * Dispatch mechanics tightly reuse the impl-block pathways, not distinguished at runtime, needs no parallel path. * Tightly enforced method ownership—as per decision 5—across all facets, rigorously tested. Slice 2 carries a 'rebuild' hint in its commit note, indicating previous rewrites now shelved in favor of the cleaner final version. ## What's Next? Half of our six slices are ready and on submain. We're locked in with declarations, coherence, contract checking, `Self` resolution, core ownership rules, and interpreter dispatch. On deck are IR lowering for gene/phen constructs (vital for JIT backend handling), operator overloading, and the rollout of generics v3 type bounds, all part of the 0.3.4 roadmap. Sure, `submain` is running 15 commits ahead of `main`, and the merge holds off while the 0.3.4 sprint drums on. Eventually, though, we need to consider the inherent risks of a ballooning batch size. Plus, issue #3 (explicit return paired with trailing expressions) remains open and is currently untouched with attention shifted toward the gene/phen sprint. **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-07-21_

Gene/phen trait system slices 2 and 3 landed on submain, adding contract checking, Self resolution, method-ownership rules, and interpreter dispatch for phen method calls.

Fifth day of sustained pause between gene/phen design completion and implementation start, with submain's 13-commit batch still awaiting merge.

Four commits on submain closing two known issues and two semantic audit findings, recovering 5 JIT fixtures and tightening scope and width-range enforcement.

v0.3.1 shipped with Handle core, pattern matching first slices, the f64 comparison fix, and a known-issues tracker, jumping the matrix from 292 to 321 tests.

Banning/Vending Engineering presented three options — large upsizing, targeted submain repairs, or an expanded grass waterway — with costs from roughly $11/acre/year (maintenance fund) to more than $400,000; the board agreed to contact petitioning landowners and delay a reconstruction hearing pending DNR guidance and landowner support.

Fifth consecutive quiet day with zero developer commits, while submain holds nine unmerged commits spanning Handle core, pattern matching, and float comparison fixes.