mirror of
https://github.com/golang/go.git
synced 2025-12-08 06:10:04 +00:00
encoding/json: clarify unmarshaling behaviour on bad fields
Fixes #19526 Change-Id: Ifaaf454e0e89fdf4309118c2e2e6ac0d0a43c39d Reviewed-on: https://go-review.googlesource.com/44711 Reviewed-by: Ian Lance Taylor <iant@golang.org>
This commit is contained in:
parent
a4ee95c805
commit
3cc2da6397
1 changed files with 3 additions and 1 deletions
|
|
@ -79,7 +79,9 @@ import (
|
||||||
// or if a JSON number overflows the target type, Unmarshal
|
// or if a JSON number overflows the target type, Unmarshal
|
||||||
// skips that field and completes the unmarshaling as best it can.
|
// skips that field and completes the unmarshaling as best it can.
|
||||||
// If no more serious errors are encountered, Unmarshal returns
|
// If no more serious errors are encountered, Unmarshal returns
|
||||||
// an UnmarshalTypeError describing the earliest such error.
|
// an UnmarshalTypeError describing the earliest such error. In any
|
||||||
|
// case, it's not guaranteed that all the remaining fields following
|
||||||
|
// the problematic one will be unmarshaled into the target object.
|
||||||
//
|
//
|
||||||
// The JSON null value unmarshals into an interface, map, pointer, or slice
|
// The JSON null value unmarshals into an interface, map, pointer, or slice
|
||||||
// by setting that Go value to nil. Because null is often used in JSON to mean
|
// by setting that Go value to nil. Because null is often used in JSON to mean
|
||||||
|
|
|
||||||
Loading…
Add table
Add a link
Reference in a new issue