• Daniel Martí's avatar
    encoding/json: use panics for phase errors · b2fcfc1a
    Daniel Martí authored
    Having these panic-like errors used to be ok, since they were used in
    the internal decoder state instead of passed around via return
    parameters.
    
    Recently, the decoder was rewritten to use explicit error returns
    instead. This error is a terrible fit for error returns; a handful of
    functions must return an error because of it, and their callers must
    check for an error that should never happen.
    
    This is precisely what panics are for, so use them. The test coverage of
    the package goes up from 91.3% to 91.6%, and performance is unaffected.
    We can also get rid of some unnecessary verbosity in the code.
    
    name           old time/op    new time/op    delta
    CodeDecoder-4    27.5ms ± 1%    27.5ms ± 1%   ~     (p=0.937 n=6+6)
    
    Change-Id: I01033b3f5b7c0cf0985082fa272754f96bf6353c
    Reviewed-on: https://go-review.googlesource.com/134835
    Run-TryBot: Daniel Martí <mvdan@mvdan.cc>
    Run-TryBot: Joe Tsai <thebrokentoaster@gmail.com>
    TryBot-Result: Gobot Gobot <gobot@golang.org>
    Reviewed-by: 's avatarJoe Tsai <thebrokentoaster@gmail.com>
    b2fcfc1a
Name
Last commit
Last update
..
ascii85 Loading commit data...
asn1 Loading commit data...
base32 Loading commit data...
base64 Loading commit data...
binary Loading commit data...
csv Loading commit data...
gob Loading commit data...
hex Loading commit data...
json Loading commit data...
pem Loading commit data...
xml Loading commit data...
encoding.go Loading commit data...