Unmarshaling Type difference from json package about ojg

[ohler55]

A bit longer I'm afraid.

[ohler55]

It is good enough to play around with. I am making my way through unit tests now and will have some changes in the top level (ojg) package but all those functions are for shared internal use only. If you run into anything you would like changed let me know and we can discuss it.

[ohler55]

v1.11.0 has been released.

[ohler55]

What you are asking for makes sense. Of course if a number in JSON is an integer then in some cases it is nice to have it be an integer in the unmarshalled result. Maybe the best of both is to have Marshal returns float64s and then leave oj.Parse to keep JSON integers as int64. What do you think of that approach?

[raidancampbell]

That seems like an excellent approach. When faced with choices for json marshaling / unmarshaling, it's been an excellent user experience to simply swap out json.Unmarshal for jsoniter.Unmarshal for oj.Unmarshal.

[ohler55]

I'm in the process of a struct Marshal speedup so I'll add that option at the same time. Look for it next week.

[ohler55]

If you don't mind working off a development version I have a branch named "pointer" that has the change in it. While the API is compatible there are a number of speedups with marshalling structs. Added more options like MustParse.

[raidancampbell]

I'm in absolutely no hurry here, for the time being I'm sticking with jsoniter's implementation. Some more pressing stuff came up in the meantime so I won't be free to test out the change for another week or two.

I appreciate the MustParse though, I'm looking forward to giving it a spin!

[raidancampbell]

It's looking like the more pressing stuff is also bound by various JSON marshaling/unmarshalings. I see the pointer branch was merged into develop recently: is that good to play around with?

[raidancampbell]

Confirmed type differences resolved, thanks for the prompt work! Unfortunately I found another unrelated discrepancy with the behavior of the standard library's json package and opened #54 for tracking