Stephen Berry
Stephen Berry
JSON pointer syntax reading also supports this in part. The main difference is that we want a core way to maintain iterators at the parsed location, for the best possible...
The new `read_allocated` option in #1027 also provides a solution for partial reading.
`read_allocated` has been renamed to `partial_read` in #1028
Thanks for bringing this up. It would be nice to be able to specify only the unknown key map and reflect on all the other values automatically. I'll keep this...
I'm moving this to discussions, because I think this issue requires more long term thought, especially as reflection in C++26 is coming. I don't want to overcomplicate the current reflection...
JSON requires UTF8, so a BOM shouldn't be needed. And, the BOM is not valid JSON for parsing into an object. So, having the BOM is technically invalid JSON. 8.1...
As I think about this more I don't really like the idea of supporting something that doesn't round-trip. @TheFeelipe, I think it might be best to make your own file...
I'm closing this, but let me know if you ever think Glaze ought to add some features around BOM handling.
Thanks for bringing this up. Right now BEVE doesn't adhere to `skip_null_members`, which it should. Will keep this issue alive until support has been added.
So, we actually want to set the value to null if a null value is read in. The reason why your BEVE and JSON do not align right now is...