The docs for big.Float, big.Int, and big.Rat specify that objects of those types shouldn't be copied (except via the appropriate .Set() method), but rather that pointers to them be used:
shallow copies of s are not supported and may lead to errors
It seems best (and fairly straightforward) to conform to those requirements.
candid82
commented
3 years ago
The docs for big.Float, big.Int, and big.Rat specify that objects of those types shouldn't be copied (except via the appropriate
.Set()method), but rather that pointers to them be used:It seems best (and fairly straightforward) to conform to those requirements.