scovich commented on issue #9204: URL: https://github.com/apache/arrow-rs/issues/9204#issuecomment-3826461477
A quick follow-up -- I turned Claude loose on the internet: * serde_json (Rust): rejects leading/repeated (and trailing) commas by design. * Arrow C++: does not enable any permissive RapidJSON flags for commas; leading/repeated commas are not accepted. * Arrow Java: configures Jackson only to allow non-numeric numbers; it does not enable permissive comma handling, so leading/repeated commas are not accepted. * RapidJSON (C++): defaults to strict JSON (no leading or repeated commas; no trailing commas). Accepts trailing commas if you explicitly pass kParseTrailingCommasFlag; even then, only trailing commas at the end of arrays/objects are allowed (not leading or repeated commas). * jq (CLI JSON processor): expects valid JSON; it does not accept “relaxed” JSON (e.g., trailing/leading/repeated commas). The FAQ recommends preprocessing with tools (JSON5/hjson/etc.) if inputs aren’t strict JSON. * JavaScript JSON.parse (ECMAScript): strictly follows the JSON grammar * simdjson (C++/bindings): parses strict JSON and rejects trailing commas; e.g., the official PHP binding’s simdjson_decode documents that trailing commas are not allowed and will throw an exception. simdjson issues further confirm errors on malformed structures like superfluous commas. tl;dr: Some other packages optionally allow trailing commas, none allow leading or repeated commas. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
