JSON tests fail on Go 1.13 about encoding HOT 3 CLOSED

There is no particular reason to use 1.13, but if it means it's not cross-compatible with other projects that run on 1.11 or higher for example. I think we should adjust the go.mod, I can make a PR for this.

from encoding.

This is a result of this change in Go1.14:

https://golang.org/doc/go1.14#encoding/json

Unfortunately, Go1.13 is now deprecated with the release of Go1.15. I could be wrong, but I believe we're taking the same approach around deprecation timelines, so (understanding I haven't read the code for this issue) I think it's unlikely to be fixed.

Is there something keeping you on Go1.13 in particular?

Edit: reading more closely, it seems like this ticket is more about Go1.13 being listed as supported by the Go mod file. Seems reasonable that we should probably bump that if this is our stance.

from encoding.

The reason the tests failed is because there was a behavior change in encoding/json in Go 1.14 that we ported to this project (see #34).

The path forward should be to update go.mod to require Go 1.14 (like @abraithwaite suggested), if you want to remain on Go 1.13 you should use segmentio/encoding v0.1.10 (although that may not be a great option since it means giving up on some bug fixes).

from encoding.