Release v0.8.1 · rsonquery/rsonpath

[0.8.1] - 2023-09-20

[breaking] Refactored the [Match]/[MatchSpan] types.
- [Match] now takes 32 bytes, down from 40.
- All fields are now private, accessible via associated functions.
- Added the len function to [MatchSpan].
Added approximate_spans result mode. (#242)
- Engine can return an approximate span of the match,
  where "approximate" means the start index is correct,
  but the end index might include trailing whitespace after the match.
- This mode is much faster that full matches, close to the performance
  of count, especially for large result sets.
- This is a library-only feature.
Library exposes a new optional feature, arbitrary.
- When enabled, includes arbitrary
  as a dependency and provides an Arbitrary impl for JsonPathQuery,
  JsonString, and NonNegativeArrayIndex.

Fixed a bug when memmem acceleration would fail for empty keys.
- This was detected by fuzzing! The query $..[""] would panic
  on certain inputs due to invalid indexing.
Fixed a panic when parsing invalid queries with wide UTF8 characters.
- This was detected by fuzzing! Parsing a query with invalid syntax
  caused by a longer-than-byte UTF-8 character would panic when
  the error handler tried to resume parsing from the next byte
  instead of respecting char boundaries.
Fixed a panic caused by node results in invalid JSON documents.
- This was detected by fuzzing! Invalid JSON documents could
  cause the NodeRecorder to panic if the apparent match span
  was of length 1.
Fixed erroneous match span end reporting. (#247)
- Fixed a bug where MatchSpan values given by the engine were
  almost always invalid.