Tyler Gregg
Tyler Gregg
Non-deterministic behavior when accessing IonValue instances from multiple threads is usually caused by violating the library's multi-threaded contract, which requires calling `makeReadOnly` in a single thread before initiating concurrent access....
Safely accessing an IonValue concurrently requires calling `makeReadOnly` in a single thread before initiating concurrent access. Violating this contract can result in non-deterministic behavior that is hard to root cause....
*Description of changes:* This library has always had auto-detection of GZIP streams built in, meaning that when users attempt to construct an `IonReader` from an `InputStream` or `byte[]`, the given...