pcollections
pcollections copied to clipboard
hrldcpr
A Persistent Java Collections Library
One of the major differences between pcollections and other persistent collections libraries like vavr is the desire to remain interoperable with the standard java collections framework. However, because persistent collections...
hi, how about the performance compare with others? any benchmark?
- [ ] if the passed list is a `Set`, then iterate over whichever set is smaller, so we get `O(mlgn)` complexity, with m
As discussed in #74, using high-level methods in loops can create lots of wrapper objects, which can reduce performance. An example of fixing this sort of thing is f58c25f. -...
`mvn clean compile -Dmaven.compiler.showDeprecation=true` …they don't indicate any actual problem, they're just because we have to implement mutators to fulfill Collections interfaces, but we have also deprecated mutators in PCollections...
as discussed in #50 we can use this benchmark to help shrink the memory footprint- https://github.com/Albul/sizeof-objects-java
We get doclint errors when running `./gradlew javadoc`, if we don't enable `Xdoclint:none` in `build.gradle` Mostly it's just `@param` fields with no description—simplest would be to just delete them entirely....
Hi there, can you please provide a version in which your interfaces do not extend mutable Java interfaces? **Example**: Right now ```PVector``` extends ```List```. This forces users to reference directly...
I am currently investigating a garbage issue created by an application using pcollections a lot. What I observed is that Iteration over an IntTree allocates plenty of Integers, as seen...
_From [[email protected]](https://code.google.com/u/100694777776169671086/) on 2009-03-16T21:43:16Z_ should be relatively easy to duplicate one of the other Java-vs-PCollections random tests. _Original issue: http://code.google.com/p/pcollections/issues/detail?id=2_
