Is any way to handle large integer parsing?

[ns-kliu]

As #29 said, gjson is parsing integer to float64

gjson/gjson.go

Lines 68 to 69 in 4d23028

	// Num is the json number
	Num float64

But it's causing a side effect for my use case that accessing by gjson and sjson like this:

	s := `{"id": 3884520826190075694}`
	n := `[]`
	n, _ = sjson.Set(n, "0", gjson.Parse(s).Value())
	fmt.Println(n) // [{"id":3884520826190076000}]

Is any way to handle large integer parsing? Really appreciate it.

[ccoVeille]

Integer/float is never fun.

Float64 is the type that can fit all others.

But float64 leads to precision errors.

But here, your number fits in an int64

https://go.dev/play/p/GrdWttFHXFl

So, the code behave badly.

You have to consider this architecture logic. A number this big will be sent via the JSON, and someone will read it.

Numbers in JSON are all floats is we refer to the RFC

So, the clients might face the same imprecision with float depending on the clients implementation of the JSON parsing.

While there is a legitimate logic in thinking there is a bug that could be fixed in gjson lib, I would encourage you to reconsider your data structure and use a string to transport such a big number.