failure_mode: Moved to extract_options. A parse error does not
have a failure mode of any significance. Skipping over a token is
dangerous at best. However, an extraction error can logically have
on_error::fail_immediately and on_error::collect_all options
(on_error::ignore has been removed, as it was deeply misguided).
max_failures: Moved to extract_options.
string_encoding: Removed encoding::cesu8
number_encoding: Removed entirely -- allowing leading zeros is
confusing in the first place.
comma_policy: Removed entirely -- treating trailing commas as
whitespace is dangerous and slows the parser down
max_structure_depth: Changed to an optional, which will fall back
to k::max_structure_depth more explicitly.
require_document: Kept.
complete_parse: Kept.
comments: Kept.
This re-enabled various unit tests that had been commented out, as the
parser options can be respected.
…options`
Altered the fields of
parse_options:failure_mode: Moved toextract_options. A parse error does not have a failure mode of any significance. Skipping over a token is dangerous at best. However, an extraction error can logically haveon_error::fail_immediatelyandon_error::collect_alloptions (on_error::ignorehas been removed, as it was deeply misguided).max_failures: Moved toextract_options.string_encoding: Removedencoding::cesu8number_encoding: Removed entirely -- allowing leading zeros is confusing in the first place.comma_policy: Removed entirely -- treating trailing commas as whitespace is dangerous and slows the parser downmax_structure_depth: Changed to anoptional, which will fall back tok::max_structure_depthmore explicitly.require_document: Kept.complete_parse: Kept.comments: Kept.This re-enabled various unit tests that had been commented out, as the parser options can be respected.