Owen Shepherd

@ul would we want to stitch them back into a single response for the editor? Some LS features might be more computationally expensive than others. If we stitch them back...

I guess I'm unsure why it works without the do block. I would have thought the lexer would only detect the end of `f` when it sees function `g`, which...

Looks like @maxbrunsfeld is a collaborator on the `npm` package. @wenkokke Do you want to wait for https://github.com/tree-sitter/tree-sitter-haskell/issues/69, or is your ERROR node non-fatal?

That's interesting, you can try running a `-DDEBUG` build, and see what the first few tokens the scanner produces are?

I'll give it a go. I've documented `-DDEBUG` in `enable scanner debug output` [here](https://github.com/tree-sitter/tree-sitter-haskell/pull/71)

Parsing `examples/postgrest/test/Main.hs` passes if you delete either both `let` statements, or the `spec $ do ...` block

I've created a list of the (smallest to largest) files that fail to parse under wasm: ``` { for i in examples/**/*.hs; do out="$(2>&1 ./script/tree-sitter-parse.js $i)"; if echo "$out" |...

Thanks @maxbrunsfeld, that sounds very plausible. I wonder if I ~halve~ double the indentation on those files whether they'll break with the native parser... **edit** they didn't

~@nkartashov I've added a preferences option, and implemented append-mode writing, in this branch: https://github.com/414owen/haskeline/tree/history-flushing-tweaks You're welcome to merge those changes into this pr~ Update: see https://github.com/judah/haskeline/pull/148

:wave: @judah