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

Use Eclipse Collections #3023

Closed
koppor opened this issue Jul 18, 2017 · 4 comments
Closed

Use Eclipse Collections #3023

koppor opened this issue Jul 18, 2017 · 4 comments
Assignees
Labels
type: code-quality Issues related to code or architecture decisions

Comments

@koppor
Copy link
Member

koppor commented Jul 18, 2017

Context: #2837, #2533, #2247

Eclipse Collections seem to be be more memory efficient than standard Java Implementations.

Should we try to switch to Eclipse Collections?

grafik

grafik

grafik

@koppor koppor added type: code-quality Issues related to code or architecture decisions status: devcall labels Jul 18, 2017
@Siedlerchr
Copy link
Member

Siedlerchr commented Jul 18, 2017 via email

@koppor
Copy link
Member Author

koppor commented Jul 18, 2017

Fir the first months, I would just use their implementations and rely on the normal Java interfaces. (Is that item 18 of Effective Java?)

Thus, it would be "just" another dependency. 😇

@koppor koppor self-assigned this Jul 18, 2017
@koppor
Copy link
Member Author

koppor commented Jul 19, 2017

@koppor koppor added the on-hold label Jul 20, 2017
@koppor
Copy link
Member Author

koppor commented Jul 20, 2017

We are currently trying to focus on other things. 🔥
We will come back later to this topic, therefore closing adding on-hold label and closing the issue for now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: code-quality Issues related to code or architecture decisions
Projects
None yet
Development

No branches or pull requests

2 participants