3 ms·
Maybe there are ideas that can be used without changing the API surface at all? I don't think grandparent is proposing the Go developers just drop the thing in
by loeg 7y ago
Maybe there are ideas that can be used without changing the API surface at all? I don't think grandparent is proposing the Go developers just drop the thing in as-is without any evaluation of fitness or backwards compatibility. Part of the significance of this work is that (they claim) it is API-compatible with the stdlib version (modulo error messages, which can be addressed).
Edit: Then again, the authors advocate mildly against upstreaming it:
> For these reasons, we also don't believe that this code should be ported upsteam to the standard encoding/json package.
https://github.com/segmentio/encoding/tree/master/json#trade-offs https://github.com/segmentio/encoding/tree/master/json#trade...