On Mon, Aug 10, 2009 at 2:35 PM, Greg Brown<[email protected]> wrote: > - Simplified debugging. It is much easier to browse a native Pivot > ArrayList's contents than a wrapped java.util.ArrayList. I expect the same > to be true for maps and sets.
Sounds like a long shot reasoning: java.util.ArrayList has been tested by millions of folks, chances of finding a bug in any of the core Java collections are slim to naught. Conversely, a bug in a new implementation is more likely to happen, especially if it has been tested by only a couple of hundred folks. > - Code independence. We designed these classes as replacements for the JDK > collections. It seems backwards to require them as a dependency. You already require Java for running Pivot. It seems backwards to introduce something that is readily available on both sides of the line, and are already used in any other library, and developers code. Just my $0.02 as a developer. Martijn
