compat/json: Correctly handle syntax-error-in-decode

1 files changed, 14 insertions, 0 deletions

diff --git a/ReleaseNotes.md b/ReleaseNotes.md
index a8496e0..5e8dab7 100644
--- a/ReleaseNotes.md
+++ b/ReleaseNotes.md
@@ -13,6 +13,11 @@
         default, add a `CompactFloats` ReEncoderConfig option to
         control this.
 
+      + Decoder: Decoding `json.Unmarshaler` or `lowmemjson.Decodable`
+        as a top-level value no longer needs to read past the closing
+        `"`/`]`/`}`; this can be significant when reading streaming
+        input, as that next read may block.
+
    - Compatibility bugfixes:
 
       + compat/json.Valid: No longer considers truncated JSON
@@ -32,6 +37,15 @@
       + compat/json.Indent: Preserve trailing whitespace, same as
         `encoding/json`.
 
+      + compat/json.Decoder: No longer transforms "unexpected EOF"
+        errors to "unexpected end of JSON input".  This makes it
+        different than `compat/json.Unmarshal`, but the same as
+        `encoding/json`.
+
+      + compat/json.Decoder, compat/json.Unmarshal: No longer mutate
+        the target value at all if there is a syntax error in the
+        input.
+
    - Unicode:
 
       + Feature: Encoder, ReEncoder: Add an `InvalidUTF8`