Possible Loss of Precision - not caused by type conversion

[Patricia Shanahan]

Roedy Green wrote:
....

So what we might see is a BigArrayList which works just like ArrayList
with long indexes. It would likely handle allocate ram 64K or so at a
pop as needed, so it would work for some types of sparce array.

....

But what about dense large arrays? There is no particular reason to
assume that large arrays are sparse. A lot are not.

Patricia

 

[bugbear]

Roedy Green wrote:
...
...

But what about dense large arrays? There is no particular reason to
assume that large arrays are sparse. A lot are not.

Roedy's idea also improves the operation needed to *grow* such
an array, assuming the final size was not known at constructor time.

BugBear

 

[Twisted]

Roedy's idea also improves the operation needed to *grow* such
an array, assuming the final size was not known at constructor time.

Want huge, dense or sparse arrays indexed by e.g. BigIntegers right
now without waiting for Sun? Use a TreeMap<BigInteger, Foo>...log n
instead of constant access time is the price you pay though.