Make great documentation goal 1.2, and plan the README's reorganisation and the nested-template gaps #33
+2
-3
@@ -383,9 +383,8 @@ value, a range check is one comparison, and `1{digits(2)}` is a second spelling
|
||||
|
||||
`{/src.score}` renders exactly what `src.score` draws, and so do `{s.score}` where `s` is
|
||||
bound to `/src` and `{p}` where `p` is bound to the column `place` of its own record, so it
|
||||
takes that column's datatype and null rather than restating them, and a `datatype`
|
||||
restating the one it takes is a second spelling. Any other `datatype` still types the values — the one way to
|
||||
type a column someone else wrote.
|
||||
takes that column's datatype and null. A `datatype` of its own, `string` included, wins
|
||||
over the one it reads: the one way to type a column someone else wrote.
|
||||
|
||||
## A typed column's calc is refused unless proven
|
||||
|
||||
|
||||
Reference in New Issue
Block a user