e7662c2213
Also simplify the test so we call `utf16_iterate` directly. Calling
`utf16_iterate` via `SpyInput` and `ts_document_parse` doesn't seem to reliably
trigger the problem using valgrind.
valgrind also doesn't detect the problem if we use a string literal like:
`utf16_iterate("", 1, &code_point);`
|
||
|---|---|---|
| .. | ||
| document_test.cc | ||
| lexer_test.cc | ||
| node_test.cc | ||
| parser_test.cc | ||
| stack_test.cc | ||
| tree_test.cc | ||