diff options
author | bors[bot] <bors[bot]@users.noreply.github.com> | 2018-01-28 09:07:26 +0000 |
---|---|---|
committer | bors[bot] <bors[bot]@users.noreply.github.com> | 2018-01-28 09:07:26 +0000 |
commit | bec9f091348386a38489110a26b279f752163034 (patch) | |
tree | 90ea82001ee09739ffa542d2a0a1bbb985559bb7 /src/parser/event_parser | |
parent | 092f9a6b98a1b0b4724888f7b24bac6f6c5c1b79 (diff) | |
parent | d3dedcace8a5fb1f047ecad05d23dce8745252d5 (diff) |
Merge #18
18: Comments r=matklad a=matklad
Diffstat (limited to 'src/parser/event_parser')
-rw-r--r-- | src/parser/event_parser/mod.rs | 47 |
1 files changed, 47 insertions, 0 deletions
diff --git a/src/parser/event_parser/mod.rs b/src/parser/event_parser/mod.rs index 65aea017b..7823c476c 100644 --- a/src/parser/event_parser/mod.rs +++ b/src/parser/event_parser/mod.rs | |||
@@ -4,17 +4,64 @@ use {SyntaxKind, Token}; | |||
4 | mod parser; | 4 | mod parser; |
5 | mod grammar; | 5 | mod grammar; |
6 | 6 | ||
7 | /// `Parser` produces a flat list of `Event`s. | ||
8 | /// They are converted to a tree-structure in | ||
9 | /// a separate pass, via `TreeBuilder`. | ||
7 | #[derive(Debug)] | 10 | #[derive(Debug)] |
8 | pub(crate) enum Event { | 11 | pub(crate) enum Event { |
12 | /// This event signifies the start of the node. | ||
13 | /// It should be either abandoned (in which case the | ||
14 | /// `kind` is `TOMBSTONE`, and the event is ignored), | ||
15 | /// or completed via a `Finish` event. | ||
16 | /// | ||
17 | /// All tokens between a `Start` and a `Finish` would | ||
18 | /// become the children of the respective node. | ||
19 | /// | ||
20 | /// For left-recursive syntactic constructs, the parser produces | ||
21 | /// a child node before it sees a parent. `forward_parent` | ||
22 | /// exists to allow to tweak parent-child relationships. | ||
23 | /// | ||
24 | /// Consider this path | ||
25 | /// | ||
26 | /// foo::bar | ||
27 | /// | ||
28 | /// The events for it would look like this: | ||
29 | /// | ||
30 | /// | ||
31 | /// START(PATH) IDENT('foo') FINISH START(PATH) COLONCOLON IDENT('bar') FINISH | ||
32 | /// | /\ | ||
33 | /// | | | ||
34 | /// +------forward-parent------+ | ||
35 | /// | ||
36 | /// And the tree would look like this | ||
37 | /// | ||
38 | /// +--PATH---------+ | ||
39 | /// | | | | ||
40 | /// | | | | ||
41 | /// | '::' 'bar' | ||
42 | /// | | ||
43 | /// PATH | ||
44 | /// | | ||
45 | /// 'foo' | ||
46 | /// | ||
47 | /// See also `CompleteMarker::precede`. | ||
9 | Start { | 48 | Start { |
10 | kind: SyntaxKind, | 49 | kind: SyntaxKind, |
11 | forward_parent: Option<u32>, | 50 | forward_parent: Option<u32>, |
12 | }, | 51 | }, |
52 | |||
53 | /// Complete the previous `Start` event | ||
13 | Finish, | 54 | Finish, |
55 | |||
56 | /// Produce a single leaf-element. | ||
57 | /// `n_raw_tokens` is used to glue complex contextual tokens. | ||
58 | /// For example, lexer tokenizes `>>` as `>`, `>`, and | ||
59 | /// `n_raw_tokens = 2` is used to produced a single `>>`. | ||
14 | Token { | 60 | Token { |
15 | kind: SyntaxKind, | 61 | kind: SyntaxKind, |
16 | n_raw_tokens: u8, | 62 | n_raw_tokens: u8, |
17 | }, | 63 | }, |
64 | |||
18 | Error { | 65 | Error { |
19 | message: String, | 66 | message: String, |
20 | }, | 67 | }, |