torque
1d65b072ee
finally the flow parser has been "integrated" with the main parser in that they now share a stack. The bigger thing is that the parsing has been decoupled from the tokenization, which will allow parsing documents without loading them fully into memory first. I've been calling this the streaming parser, but it's worth noting that I am referring to streaming input, not streaming output. It would certainly be possible to do streaming output, but I am not interested in that at the moment (it would be the lowest-memory-overhead approach, but it's a lot of work for little gain, and it is less flexible for converting input to objects).