v3.3.0

Non-null terminated buffers!

JSON

Non-null terminated buffer reading when using glz::read<glz::opts{.null_terminated = false}>.

In order to not introduce any breaking changes glz::read_json (using default glz::opts) has null_terminated = true.

The default behavior requires null termination for maximum performance.

glz::prettify_json and glz::minify_json also support non-null terminated buffers.

BEVE (binary)

For BEVE we don't care whether a buffer is null terminated anymore, we just always handle the data as if it is not, because we wouldn't get significant performance improvements like we do with JSON. The reason is that a null character is valid binary so we can't make decisions on this value.

What's Changed

• Support for non-null terminated buffers when parsing JSON and BEVE by @stephenberry in #1262

Full Changelog: v3.2.6...v3.3.0