diff options
author | bors[bot] <26634292+bors[bot]@users.noreply.github.com> | 2020-08-10 20:38:19 +0100 |
---|---|---|
committer | GitHub <[email protected]> | 2020-08-10 20:38:19 +0100 |
commit | b050937c1071e68a4ade69375f1f17b703cafb02 (patch) | |
tree | 64a2478b161bdeb32ea73876acf3afcbc9dcb84b /docs | |
parent | 1e310575e3df3104641044e0285def65edc3f819 (diff) | |
parent | ff60fdc315e324843589554f45e2e3c8f7cd1bf4 (diff) |
Merge #5703
5703: Fix typos in syntax.md r=kjeremy a=lnicola
Closes #5700
Co-authored-by: Laurențiu Nicola <[email protected]>
Diffstat (limited to 'docs')
-rw-r--r-- | docs/dev/syntax.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/dev/syntax.md b/docs/dev/syntax.md index d4bc4b07c..f1bcdc4af 100644 --- a/docs/dev/syntax.md +++ b/docs/dev/syntax.md | |||
@@ -74,7 +74,7 @@ Points of note: | |||
74 | * The original text can be recovered by concatenating the texts of all tokens in order. | 74 | * The original text can be recovered by concatenating the texts of all tokens in order. |
75 | * Accessing a child of particular type (for example, parameter list of a function) generally involves linerary traversing the children, looking for a specific `kind`. | 75 | * Accessing a child of particular type (for example, parameter list of a function) generally involves linerary traversing the children, looking for a specific `kind`. |
76 | * Modifying the tree is roughly `O(depth)`. | 76 | * Modifying the tree is roughly `O(depth)`. |
77 | We don't make special efforts to guarantree that the depth is not liner, but, in practice, syntax trees are branchy and shallow. | 77 | We don't make special efforts to guarantee that the depth is not linear, but, in practice, syntax trees are branchy and shallow. |
78 | * If mandatory (grammar wise) node is missing from the input, it's just missing from the tree. | 78 | * If mandatory (grammar wise) node is missing from the input, it's just missing from the tree. |
79 | * If an extra erroneous input is present, it is wrapped into a node with `ERROR` kind, and treated just like any other node. | 79 | * If an extra erroneous input is present, it is wrapped into a node with `ERROR` kind, and treated just like any other node. |
80 | * Parser errors are not a part of syntax tree. | 80 | * Parser errors are not a part of syntax tree. |