8e8fbc4cff
fixing issue 1480 ( #1485 )
2021-03-08 19:31:42 -05:00
bcab8d3abf
Check for end object/array at top level
...
This avoids a very unlikely buffer overrun that can occur in a particular kind of invalid JSON:
- the document is invalid with an unclosed top level array or object
- the last thing in the document is a number that ends at EOF
- the padding is filled entirely with numeric digits
2021-02-22 09:35:21 -08:00
1bfbb6448a
Check out-of-order error in object index
2021-01-26 20:49:14 -08:00
e6d2b7759a
Fix assertion when getting array after failing to get a scalar
...
Also remove distinction between & and && for array start, acting like
other types
2021-01-26 14:09:54 -08:00
55faf4c5bc
Recommend simdjson::ondemand over simdjson::builtin::ondemand ( #1380 )
...
Co-authored-by: Daniel Lemire <lemire@gmail.com >
2021-01-14 17:33:49 -05:00
195acc3e45
Add find_field / find_field_unordered to object
2020-12-20 11:39:50 -08:00
d670906ff3
Don't keep a separate at_start boolean in object
2020-12-15 11:29:31 -08:00
f9c6dedca1
Add test for out-of-order parse asserts
2020-12-13 13:39:47 -08:00
db6bf15361
Allow all array/object/etc. to be copied
2020-12-06 16:29:53 -08:00
3aa3175378
Add tests for recovering from partial child iteration
2020-12-06 16:19:06 -08:00
4c63956624
Enable object["x"]["y"]
2020-12-06 15:23:52 -08:00
c89647af9e
Make all values use same underlying iterator
2020-12-06 15:23:52 -08:00
1303a88769
Unconditionally track depth
2020-12-06 15:23:52 -08:00
af4db55e66
remove trailing whitespace ( #1284 )
2020-11-03 21:48:09 +01:00
88f0dc4726
Add API docs, ensure parser and field methods called with &
2020-10-06 11:29:45 -07:00
a700848bae
Move ondemand implementation to include/
2020-10-04 12:47:30 -07:00
Daniel Lemire