Answer prose round 2: one word for the escape, the goal and its conflict in two sentences, and a plainer item 114
This commit is contained in:
+5
-5
@@ -844,8 +844,8 @@ table's rows stop reading any engine type once items 101 and 102 remove those re
|
|||||||
|
|
||||||
## Goal 5.1's `{…}` covers `{{`, `}}` and a lone `}`, so the goal names no escape
|
## Goal 5.1's `{…}` covers `{{`, `}}` and a lone `}`, so the goal names no escape
|
||||||
|
|
||||||
2026-10-05, Lilleman auf Larv. Serves goal 5.1, which says everything outside `{…}` prints
|
2026-10-05, Lilleman auf Larv. Serves goal 5.1: everything outside `{…}` prints exactly as
|
||||||
exactly as written, yet `{{` prints `{`, `}}` prints `}`, and a lone `}` is a load error naming
|
written. Yet `{{` prints `{`, `}}` prints `}`, and a lone `}` is a load error naming `}}`, as
|
||||||
`}}`, as the README's Format string section states. The maintainer ruled the escape implicit in the
|
the README's Format string section states. The maintainer ruled the escape implicit in the
|
||||||
goal: doubled braces and a lone `}` 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 escape and
|
||||||
stays an error. Valid while a template escapes a brace by doubling it.
|
a lone `}` stays an error. Valid while a template escapes a brace by doubling it.
|
||||||
|
|||||||
@@ -385,7 +385,7 @@ Require the path step to reach a sibling category.
|
|||||||
|
|
||||||
### 114. Settle whether goal 7.2's "no escaping" holds for a first template with a literal brace, which must write `{{` or `}}`.
|
### 114. Settle whether goal 7.2's "no escaping" holds for a first template with a literal brace, which must write `{{` or `}}`.
|
||||||
|
|
||||||
The decision "Goal 5.1's `{…}` covers `{{`, `}}` and a lone `}`, so the goal names no escape" keeps a lone `}` a load error. Goal 7.2 promises a first template needs no escaping; the maintainer decides whether that means shell quoting only, or also the doubled brace.
|
Under the decision "Goal 5.1's `{…}` covers `{{`, `}}` and a lone `}`, so the goal names no escape", a literal brace is written `{{` or `}}`, and a lone `}` is a load error. Goal 7.2 promises a first template needs no escaping. The maintainer decides whether the escaping it rules out is shell quoting only, or the doubled brace too.
|
||||||
|
|
||||||
### 107. Move the template engine into `internal/`, leaving the root the public API and its options.
|
### 107. Move the template engine into `internal/`, leaving the root the public API and its options.
|
||||||
|
|
||||||
|
|||||||
Reference in New Issue
Block a user