Repository navigation

One spelling for one record declaration: `type X = { .. }` stops lowering to a positional tuple - #9058

Merged

briansrls merged 6 commits into

mainfrom

session/vivid-boar-345

Aug 24, 2026

Merged

One spelling for one record declaration: `type X = { .. }` stops lowering to a positional tuple#9058
briansrls merged 6 commits into
mainfrom
session/vivid-boar-345

Commits on Aug 23, 2026
- One spelling for one record declaration: `type X = { .. }` stops lowering to a positional tuple
  
  gunbc-ci-auto-heal
  and
  claude
  committed
  e34fe55
Commits on Aug 24, 2026
- Merge origin/main into session/vivid-boar-345
  gunbc-ci-auto-heal
  committed
  730741b
- Thread `sole_constructor` through the `=` spelling too: the modifier was consumed and silently dropped
  
  gunbc-ci-auto-heal
  and
  claude
  committed
  6d29d40
- Close the field-count carve-out too, and declare the one modifier drop that is not this change's to close
  
  gunbc-ci-auto-heal
  and
  claude
  committed
  ad1a182
- Name the next-rung trigger for the declared modifier drop, in trigger form
  
  gunbc-ci-auto-heal
  and
  claude
  committed
  b55f398
- Merge origin/main into session/vivid-boar-345
  gunbc-ci-auto-heal
  committed
  67c559b