diff options
| author | Johann Hemmann <johann.hemmann@code.berlin> | 2024-01-08 18:10:48 +0100 |
|---|---|---|
| committer | Johann Hemmann <johann.hemmann@code.berlin> | 2024-01-08 18:10:48 +0100 |
| commit | d94f572fe249e1adc95a2dc876cc9f1d028c47bb (patch) | |
| tree | 9e1d9e9e2ed5c15494f6cb517e9f68b30b601ff0 /docs/dev | |
| parent | c1c242180e72dba84b53cc554992e275a1dc5291 (diff) | |
| download | rust-d94f572fe249e1adc95a2dc876cc9f1d028c47bb.tar.gz rust-d94f572fe249e1adc95a2dc876cc9f1d028c47bb.zip | |
Remove newline and add dot
Diffstat (limited to 'docs/dev')
| -rw-r--r-- | docs/dev/syntax.md | 3 |
1 files changed, 1 insertions, 2 deletions
diff --git a/docs/dev/syntax.md b/docs/dev/syntax.md index 97e376787c8..fd6f220f4fa 100644 --- a/docs/dev/syntax.md +++ b/docs/dev/syntax.md @@ -41,7 +41,6 @@ Syntax trees are a semi-transient data structure. In general, frontend does not keep syntax trees for all files in memory. Instead, it *lowers* syntax trees to more compact and rigid representation, which is not full-fidelity, but which can be mapped back to a syntax tree if so desired. - ### GreenNode GreenNode is a purely-functional tree with arbitrary arity. Conceptually, it is equivalent to the following run of the mill struct: @@ -500,7 +499,7 @@ Specifically, `TreeSink` constructs the tree in lockstep with draining the origi In the process, it records which tokens of the tree correspond to which tokens of the input, by using text ranges to identify syntax tokens. The end result is that parsing an expanded code yields a syntax tree and a mapping of text-ranges of the tree to original tokens. -To deal with precedence in cases like `$expr * 1`, we use special invisible parenthesis, which are explicitly handled by the parser +To deal with precedence in cases like `$expr * 1`, we use special invisible parenthesis, which are explicitly handled by the parser. ### Whitespace & Comments |