1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
// Trivet
// Copyright (c) 2025 by Stacy Prowell. All rights reserved.
// https://gitlab.com/binary-tools/trivet
//! Parse comments in various forms.
use crateParserCore;
use Box;
/// Parse comments in various common forms. Several common comment forms are understood.
///
/// |Comment Style |Flag |Default |
/// |---------------|--------------------|--------|
/// |`/* ... */` |`enable_c` |true |
/// |`// ...` |`enable_cpp` |true |
/// |`<# ... #>` |`enable_powershell` |false |
/// |`# ...` |`enable_python` |false |
/// |`<!-- ... -->` |`enable_xml` |false |
///
/// To use, create a new instance with [`CommentParser::new`] and then enable or disable
/// flags, depending on what comment forms you want to process. Finally, use the
/// [`CommentParser::process`] method to consume all comments and whitespace.
///
/// In addition to these comment forms, you can add your own. Define a method that does
/// the following.
///
/// - Accepts a [`ParserCore`] instance
/// - Consumes any comments you wish
/// - Returns `true` if any comments are consumed
///
/// The return value is important; it is used to determine when all comments have been
/// consumed for [`CommentParser::process`].
///
/// Set the `custom` field to a `Box` instance containing your method, and then set
/// `enable_custom` to true.
///
/// The following is an example that parses Lua comments, which are a bit notorious
/// for being persnickety. `--[[` starts a multi-line comment, but `---[[` starts
/// a single-line comment (because the `--` begins a single line comment unless
/// immediately followed by `[[`).
///
/// ```rust
/// use trivet::parse_from_string;
/// use trivet::Parser;
/// use trivet::ParserCore;
/// use trivet::parsers::comments::CommentParser;
///
/// let mut parser = parse_from_string("--[[ I am a long\nLua comment. --]]");
/// let mut compar = CommentParser::new();
/// compar.enable_c = false;
/// compar.enable_cpp = false;
/// compar.custom = Box::new(
/// |parser: &mut ParserCore| -> bool {
/// if parser.peek_and_consume_chars(&['-','-','[','[']) {
/// parser.take_until("--]]");
/// true
/// } else if parser.peek_and_consume_chars(&['-','-']) {
/// parser.take_while(|ch| ch != '\n');
/// true
/// } else {
/// false
/// }
/// }
/// );
/// compar.enable_custom = true;
/// compar.process(&mut parser.borrow_core());
/// #[cfg(not(feature = "no_tracking"))]
/// assert_eq!(parser.loc().to_string(), "<string>:2:18");
/// assert!(parser.is_at_eof());
/// ```
///
/// The `#[cfg]` is required so this documentation test will pass with `no_tracking` enabled.