Motivation
While integrating pure-simdjson@v0.1.4, the README and example_test.go were thin on the DOM iteration surface and numeric typing. The following were not easy to pin down without reading element.go directly:
Object.Iter() / ObjectIter (Next() / Key() / Value()) and whether iteration is document order (it is — worth stating explicitly, since it affects reproducibility for consumers).Array.Iter() / ArrayIter shape.- The full
Type() constant set (TypeNull / TypeBool / TypeInt64 / TypeUint64 / TypeFloat64 / TypeString / TypeArray / TypeObject) and the int64-vs-uint64-vs-float classification rules.
Request
A short "Walking the DOM" section in the README (or godoc examples) covering ordered object/array iteration and the numeric type tags. Low effort, high leverage for integrators building parity-sensitive adapters on top of the DOM API.
Motivation
While integrating
pure-simdjson@v0.1.4, the README andexample_test.gowere thin on the DOM iteration surface and numeric typing. The following were not easy to pin down without readingelement.godirectly:Object.Iter()/ObjectIter(Next()/Key()/Value()) and whether iteration is document order (it is — worth stating explicitly, since it affects reproducibility for consumers).Array.Iter()/ArrayItershape.Type()constant set (TypeNull/TypeBool/TypeInt64/TypeUint64/TypeFloat64/TypeString/TypeArray/TypeObject) and the int64-vs-uint64-vs-float classification rules.Request
A short "Walking the DOM" section in the README (or godoc examples) covering ordered object/array iteration and the numeric type tags. Low effort, high leverage for integrators building parity-sensitive adapters on top of the DOM API.