Feature: Incremental Parsing

[dashbitco]

Feature: Incremental Parsing

[josevalim]

@jjl the issue is that we heavily inline code nimble_parsec. So for example, the datetime parser in the readme, when given something like "2010-04-17T" will return an error while it is just incomplete, since we attempt to match everything or nothing at all. So basically, you'd need to track completion on the side, because you simply can't rely on nimble_parsec to do that.

I wouldn't oppose if the :error tuple returns a new element, which is an anonymous function representing the parsing stack. This anonymous function can be invoked again with a binary to resume parsing. This should be cheap enough so we can always do it without hiding it behind an option.

Then we need tests for each combinator. Once this is done, it should be good for merging. A PR is appreciated.

Thanks!

[josevalim]

Ping?

[jjl]

As discussed in IRC just now, I think it's a good direction to go in, but I haven't had the time to work on it recently. Hopefully the big crunch I'm under right now will lift a bit soon.

[josevalim]

Closing this for now.