aboutsummaryrefslogtreecommitdiff
path: root/test/unit/viml/expressions/parser_spec.lua
Commit message (Collapse)AuthorAge
* unittests: Avoid alloc log checking errors when printing testsZyX2017-10-29
|
* viml/parser/expressions: Fix last error found by KLEEZyX2017-10-29
|
* viml/parser/expressions: Fix some errors spotted by KLEEZyX2017-10-19
| | | Not all of them are fixed yet though.
* unittests: Free everything and check for memory leaksZyX2017-10-16
| | | Also improves error reporting.
* viml/parser/expressions: Highlight prefix separately from numberZyX2017-10-16
| | | Should make accidental octals more visible.
* charset: Avoid overflow in vim_str2nrZyX2017-10-16
|
* viml/parser/expressions,klee: Fix some problems found by KLEE runZyX2017-10-15
|
* viml/parser/expressions,tests: Add AST freeing, with sanity checksZyX2017-10-15
|
* unittests: Test some edge casesZyX2017-10-15
|
* viml/parser/expressions: Create tests for latest additionsZyX2017-10-15
|
* viml/parser/expressions: Finish parserZyX2017-10-15
| | | | | | | Note: formatc.lua was unable to swallow some newer additions to ExprASTNodeType (specifically `kExprNodeOr = '|'` and probably something else), so all `= …` were dropped: in any case they only were there in order to not bother updating viml_pexpr_debug_print_ast_node and since it is now known all nodes which will be present it is not much of an issue.
* viml/parser/expressions: Add support for string parsingZyX2017-10-15
|
* viml/parser/expressions: Add support for subscript and list literalsZyX2017-10-15
|
* viml/parser/expressions: Error out on multiple colons in a rowZyX2017-10-15
|
* viml/parser/expressions: Add support for the dot operator and numbersZyX2017-10-15
|
* viml/parser/expressions: Add support for comparison operatorsZyX2017-10-15
|
* viml/parser/expressions: Make sure that arrows outside lambda throwZyX2017-10-15
|
* viml/parser/expressions: Add support for ternary operatorZyX2017-10-15
|
* viml/parser/expressions: Fix determining invalid commas/colonsZyX2017-10-15
|
* viml/parser/expressions: Fix call inside nested parenthesisZyX2017-10-15
| | | | It may have incorrectly tried to call everything because of essentially “value” nodes being treated as not such.
* unittests: Add support for dumping “expected” stateZyX2017-10-08
| | | Purpose is similar to that of `screen:snapshot_util()`, but in different domain.
* viml/parser/expressions: Make curly braces name actually workZyX2017-10-08
|
* viml/parser/expressions: Make commas actually work when callingZyX2017-10-08
|
* viml/parser/expressions: Make commas actually work when callingZyX2017-10-08
|
* viml/parser/expressions: Add support for figure braces (three kinds)ZyX2017-10-08
|
* viml/parser/expressions: Start creating expressions parserZyX2017-10-08
Currently supported nodes: - Register as it is one of the simplest value nodes (even numbers are not that simple with that dot handling). - Plus, both unary and binary. - Parenthesis, both nesting and calling. Note regarding unit tests: it stores data for AST in highlighting in strings in place of tables because luassert fails to do a good job at representing big tables. Squashing a bunch of data into a single string simply yields more readable result.