Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

A one single collection could be more self-contained #13

Closed
Overruler opened this issue Jun 29, 2014 · 1 comment
Closed

A one single collection could be more self-contained #13

Overruler opened this issue Jun 29, 2014 · 1 comment

Comments

@Overruler
Copy link

Currently it's quite hard to pick one collection, say FastList out of the whole without pulling in with it about a billion other classes. This in turn makes any reuse with additions/changes a majorly divergent fork any way one might try to do it.

@goldmansachs
Copy link
Collaborator

Is there something you're trying to add that's missing? We could potentially add it.

The library is designed to have efficient containers plus a full featured API. The API makes it hard to tease apart the containers from the rest of the library. If we dropped support for older versions of Java and moved to Java 8, we could use virtual extension methods to make it easier to use efficient containers in isolation. Not sure when that might be, so closing the issue for now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant