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);`
|
||
|---|---|---|
| .. | ||
| compiler | ||
| fixtures | ||
| fuzz | ||
| helpers | ||
| integration | ||
| runtime | ||
| benchmarks.cc | ||
| test_helper.h | ||
| tests.cc | ||