Related proposal: #12146

@minux i experience some troubles moving from python to golang as i use integer keys a lot. The python behavior:

>>> d = {1: 1, 5: 4}
>>> json.dumps(d)
'{"1": 1, "5": 4}'
>>> d = {1.4: 1, 5.1: 4}
>>> d
{1.4: 1, 5.1: 4}
>>> json.dumps(d)
'{"1.4": 1, "5.1": 4}'

Maybe we can introduce a special method inside json module for marshalling such data?

I'm speaking about data structures not json

12 сент. 2015 г., в 13:16, Artyom Pervukhin notifications@github.com написал(а):

Why not to implement this in the default module?

I believe one reason for this is that encoding/json implements RFC 4627, which defines JSON object as

An object is an unordered collection of zero or more name/value pairs, where a name is a string and a value is a string, number, boolean, null, object, or array.

(emphasis is mine)

—
Reply to this email directly or view it on GitHub.

This week I added 100+ lines of code to one of our packages to support MarshalJSON and UnmarshalJSON map[int]OurType. I also added 130+ lines of unit tests. While in the standard lib code, I could see it would be far fewer lines based on all of the unexported types and utility functions.

I would love to add this to the standard lib. What is the process for getting an issue approved and assigned?

Did not get to this for Go 1.6, sorry. We should think about this at the same time as #12146.

@rsc, it seems like #12146 is likely to happen, and there's a CL out at https://golang.org/cl/20356.

Given that, you can make your integer keys work but you have to make your own int type with the obvious TextMarshaler/TextUnmarshaler methods.

What are your thoughts about also doing this change? I still think it's worth doing, and I'd like to send a 1.7 CL if you agree.

Bump for @rsc or anyone else with opinions. Shall I send a CL for this?

The change from #12146 has now gone in.

If the change is small and you can make it happen soon, sure.

I'll send a CL in the next couple of days.

CL https://golang.org/cl/22060 mentions this issue.