Answer prose round 1: a plainer decision title, name which braces belong to the syntax, and file goal 7.2's escaping as question 114

This commit is contained in:
2026-10-05 16:32:50 +02:00
committed by Lillem4n
parent 7ce34ba1fc
commit 533258e662
3 changed files with 10 additions and 5 deletions
+3 -3
View File
@@ -842,10 +842,10 @@ package under `internal/`, behind the import list `imports_test.go` checks. A
table's rows stop reading any engine type once items 101 and 102 remove those reads; item
102 then moves them into `internal/rows` and adds it to that list. Valid until `todo.md` item 107 moves the engine.
## Goal 5.1 counts `{{`, `}}` and a lone `}` as template syntax, so they are not text printed as written
## Goal 5.1's `{…}` covers `{{`, `}}` and a lone `}`, so the goal names no escape
2026-10-05, Lilleman auf Larv. Serves goal 5.1. Goal 5.1 says everything outside `{…}` prints
2026-10-05, Lilleman auf Larv. Serves goal 5.1, which says everything outside `{…}` prints
exactly as written, yet `{{` prints `{`, `}}` prints `}`, and a lone `}` is a load error naming
`}}`, as the README's Format string section states. The maintainer ruled the escape implicit in the
goal: the braces belong to the `{…}` syntax, so the goal names no exception and a lone `}`
goal: doubled braces and a lone `}` belong to the `{…}` syntax, so the goal names no exception and a lone `}`
stays an error. Valid while a template escapes a brace by doubling it.