tree-sitter/spec/runtime
Max Brunsfeld 1e353381ff Don't create error node in lexer unless token is completely invalid
Before, any syntax error would cause the lexer to create an error
leaf node. This could happen even with a valid input, if the parse
stack had split and one particular version of the parse stack
failed to parse.

Now, an error leaf node is only created when the lexer cannot understand
part of the input stream at all. When a normal syntax error occurs,
the lexer just returns a token that is outside of the expected token
set, and the parser handles the unexpected token.
2016-05-26 14:15:10 -07:00
..
document_spec.cc Don't create error node in lexer unless token is completely invalid 2016-05-26 14:15:10 -07:00
node_spec.cc Avoid recompiling test languages when possible 2016-03-03 12:05:04 -08:00
parser_spec.cc Don't create error node in lexer unless token is completely invalid 2016-05-26 14:15:10 -07:00
stack_spec.cc Discard tokens after error detection to find the best repair 2016-05-11 13:49:43 -07:00
tree_spec.cc Expose lower stack nodes via pop_until() function 2016-03-07 16:09:34 -08:00