Behaves differently from stdlib in map encoding about sonic HOT 4 CLOSED

Unless you mention that your library is compatible with encoding/json, I think it's good to sacrifice functionality for performance 😄

However, if you want to compare performance with other libraries, you should, to be fair, see if the library you're comparing has an option that doesn't sort the map, and use that if any.
For example, json-iterator/go supported by SortMapKeys: false at config . ( Also, my library support too by json.UnorderedMap() option )

from sonic.

Is this a documented behaviour of the standard library?

from sonic.

See https://golang.org/pkg/encoding/json/#Marshal

The map keys are sorted and used as JSON object keys by applying the following rules, subject to the UTF-8 coercion described for string values above:

from sonic.

As you know, this behavior hurts performance A LOT, and it's specific to the Go StdLib, RFC8259 does NOT require sorting the keys.

This library is designed for performance, not a drop-in replacement of the StdLib, so we must drop some performance-killing "features", as long as it still meets the requirements of the RFC, it's a working implementation. It is OK to behave slightly different with the StdLib.

For reproducible tests, we might consider making it optional. You can then manually switch it on at the cost of some performance.

BTW, if you think the benchmark result is unfair, you can always disable key sorting in your library, and benchmark again.

Marked low-priority now.

from sonic.