@doglooksgood is there a need for it still? are you using parinfer-rust?

not yet, but I want to use it. until there's changes, some issues can be fixed.

@shaunlebron @doglooksgood FWIW I’m finding the edits a source of hard-to-fix bugs. I’m planning to move to a model which returns changed lines instead of all the individual edits. This should be easier since parinfer is quite line-based.

This will mess up smart mode, won't it?

@eraserhd you’re mixing up input changes with output changes I think

input changes need to be exact to infer the right output changes

unless the output changes themselves become detected as input changes

Ahh.. Yeah, I didn't understand what Colin was saying.

@eraserhd Right, Cursive’s implementation doesn’t split the input into lines, and instead of returning another whole document returns just the edits to the original document. This greatly reduces GC pressure and is much more efficient (in IntelliJ, at least, and I’m pretty sure most editors)

But the implementation is tricky and it makes some things (like cursor holding) hard to implement. I’ve had a lot of edge case bugs as a result.

So, I have parinfer-rust building and running with WebAssembly. The wasm tools for Rust aren't quite sorted out, so it was rough. But not sure what to do next.