s2protocol-rs VS parse-rosetta-rs

I mean for example https://github.com/sebosp/s2protocol-rs/blob/755098fb86ab6b1... I hacked my way around the json protocol specification, an enum has n types, using log I can find the number of bits I need to read to uniquely identify each variant, that kind of serialization I wonder the name of.

I'm in the process of releasing the crates for nom-mpq and s2protocol, probably will do so in the coming days.

Comparing performance of parser libraries

For a very rough comparison of parsers, see https://github.com/rosetta-rs/parse-rosetta-rs

Since this takes a unique approach, would you be interested in adding it to parse-rosetta-rs? Its a repo to help users do a comparative analysis of parser crates, providing some very crude stats to help get them started and allowing them to compare what the APIs look like.

The reason I assume its unrelated to combine is that for the json implementation, a previous version of combine built in about the same time as nom

I'm tempted to collect all of these benchmark repos into a github org to make them easier to find. So far I know of parser, md, argparse, and template languages.