Skip to content

Commit 3421b40

Browse files
committed
Remove NAK from typed array
As per a dry run, it is far better if we don't have a NAK
1 parent c128497 commit 3421b40

File tree

1 file changed

+1
-3
lines changed

1 file changed

+1
-3
lines changed

docs/protocol/data-types.md

Lines changed: 1 addition & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -89,12 +89,11 @@ A flat array is currently a response specific data type (only sent by the server
8989
### Typed array
9090

9191
A typed array is like a flat array, but with the exception that it can only hold
92-
two types: either a [simple type](#simple-types) or a `NUL`. Since this array just has a specific type in its declaration, unlike flat arrays, `tsymbol`s are not required.
92+
two types: either a [simple type](#simple-types) or a `NULL`. Since this array just has a specific type in its declaration, unlike flat arrays, `tsymbol`s are not required.
9393

9494
You can think of it to be like:
9595

9696
- there is either no element (integer value of `0`; also called `NULL`)
97-
- there is an error (integer value of `21`; also called `NAK`)
9897
- or there is an element of the declared type
9998

10099
Say a programming language represents an array like:
@@ -127,7 +126,6 @@ Line-by-line explanation:
127126

128127
:::note
129128
A typed array is currently a response specific data type (only sent by the server and never by the client). The `NULL`s correspond to the cases when the server can't find the requested item.
130-
The `NAK` is context dependent.
131129
:::
132130

133131
### Any array

0 commit comments

Comments
 (0)