John Keiser

Yep, agreed block processing is the right place to go. I'm not sure we can pull it off before 1.0, though, so I'd like to find out just how much...

I have a branch, jkeiser/no-padding, which checks whether it's stepping off the end of the index buffer. That should take care of any accesses directly at EOF.

> We can possibly use templates to have both approaches. Yeah; I was thinking maybe if you provide a padded_string or padded_string_view, we return a faster `padded::document`, and if not,...

On demand could add support for this via a get_decimal and get_bigint methods (in a way that would be hard to do with the dom). I don't think it blocks...

`get_raw_json()` would absolutely be worth doing. You should be able to do your own kind of parsing if you want. For efficiency's sake, it would probably give you a string_view...

There is now a `raw_json_token` method on all JSON values, yep! Let us know if it meets your needs. We haven't done anything around specific bigint or decimal representation, and...

It's definitely a good idea to keep track of size over time ... that affects the ability to distribute. Not part of this at ALL, but someday it'll be nice...

For some reason I didn't see your response: I think it's reasonable to run this on simdjson.so at a minimum, and perhaps the parse executable. For ondemand, perhaps the partial_tweets...

@pauldreik I'm fine leaving this pr around if you plan to get back to it; otherwise let's file an issue and get back to it when we have time :)

@pauldreik do you have any idea whether the results of this are generally stable? If so, I think it'd be reasonable to reject changes with a 20% size change (or...