resolving long integers (decimal, hexadecimal, octal)

[AvdN]

There is no restriction on size of integers in the YAML specification. However resolving integers in resolve.go assumes that something like 0xDef9C64256DeE61ebf5B212238df11C7E532e3B7 is a string because parseInt fails to parse this.

Although during loading it might be acceptable to load such a value as a string, during dumping (marshalling) this leads to output errors as I noticed when trying to answer https://stackoverflow.com/q/54584832/1307905, in which the above string doesn't get quoted, although it should be.

I assume that parseInt returns with err.Err = ErrRange (resolve.go line 151), but I don't see a way to return quoting style information by the resolve function.

[felixfontein]

getsops/sops#1003 is caused basically by this: a string containing a hex number, like "0x0123456789ABCDEF0123456789ABCDEF0123456789ABCDEF0123456789ABCDEF", is converted to 0x0123456789ABCDEF0123456789ABCDEF0123456789ABCDEF0123456789ABCDEF when de- and then reserialized with go-yaml, which is then parsed as an integer by conforming YAML parsers.