You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/protocol/data-types.md
+1-3Lines changed: 1 addition & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -89,12 +89,11 @@ A flat array is currently a response specific data type (only sent by the server
89
89
### Typed array
90
90
91
91
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.
93
93
94
94
You can think of it to be like:
95
95
96
96
- there is either no element (integer value of `0`; also called `NULL`)
97
-
- there is an error (integer value of `21`; also called `NAK`)
98
97
- or there is an element of the declared type
99
98
100
99
Say a programming language represents an array like:
@@ -127,7 +126,6 @@ Line-by-line explanation:
127
126
128
127
:::note
129
128
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.
0 commit comments