On Sun, 1 Sep 2024 16:32:00 GMT, fabioromano1 wrote:
>> This implementation of MutableBigInteger.leftShift(int) optimizes the
>> current version, avoiding unnecessary copy of the MutableBigInteger's value
>> content and performing the primitive shifting only in the original portion
>> of the v
On Mon, 2 Sep 2024 16:04:14 GMT, Raffaello Giulietti
wrote:
> * I wonder if `MutableBigIntegerBox` can be reduced to just a set of
> accessors for the `MutableBigInteger` fields. Also, I guess that the
> benchmarks can be written to use the public class `BigInteger` to avoid
> having two copi
> This implementation of MutableBigInteger.leftShift(int) optimizes the current
> version, avoiding unnecessary copy of the MutableBigInteger's value content
> and performing the primitive shifting only in the original portion of the
> value array rather than in the value yet extended with trail
