Commit e76b5f9
fix(borrow): escape
…gate)
Two `print(*r)` example fragments inside doc-comment blocks (lines 1115
and 1338) contained the literal substring `(*r`, which OCaml's lexer
treats as a nested comment opener — bringing the outer comment to depth
2 with only one matching `*)` to close it. Result: "Comment not
terminated" at EOF on every `dune build`. Marker count was 126 `(*` vs
124 `*)` (off by 2, one per offending example); after this patch it is
124 / 124.
This has blocked main's `dune build` since #335 (CORE-01 pt3 Slice A)
merged, which is why every subsequent PR (#341, #344, the open #346) has
shown `build` red regardless of its own changes. Tiny fix; high
leverage.
Fix: insert a single space inside the parens — `print( *r)` — so the
lexer sees `(` `*` `r` `)` rather than the comment-open token `(*`
followed by `r`. Reader-friendly; the example still reads the same.
No behavioural change. No code touched. Comment text only.
Diagnosed by parallel claude (INT-03 / S5 thread). Refs #335
Co-authored-by: Claude <noreply@anthropic.com>(*r inside doc-comment examples (unblocks main … (#349)1 parent 6b09ed6 commit e76b5f9
1 file changed
Lines changed: 2 additions & 2 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
1112 | 1112 | | |
1113 | 1113 | | |
1114 | 1114 | | |
1115 | | - | |
| 1115 | + | |
1116 | 1116 | | |
1117 | 1117 | | |
1118 | 1118 | | |
| |||
1335 | 1335 | | |
1336 | 1336 | | |
1337 | 1337 | | |
1338 | | - | |
| 1338 | + | |
1339 | 1339 | | |
1340 | 1340 | | |
1341 | 1341 | | |
| |||
0 commit comments