-
-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
Comments
I would vote against switching as we then heavily depend on an external
library for core features and switching back would be a problem then.
Am 18.07.2017 10:55 vorm. schrieb "Oliver Kopp" <notifications@github.com>:
… Context: #2837 <#2837>, #2533
<#2533>, #2247
<#2247>
Eclipse Collections <http://www.eclipse.org/collections/> seem to be be
more memory efficient than standard Java Implementations.
Should we try to switch to
[image: grafik]
<https://user-images.githubusercontent.com/1366654/28246188-8d1ff41a-6a14-11e7-9f2f-bd6b93623c7b.png>
[image: grafik]
<https://user-images.githubusercontent.com/1366654/28246190-9c54b434-6a14-11e7-95a8-6eb2e6edf769.png>
[image: grafik]
<https://user-images.githubusercontent.com/1366654/28246189-96a460e8-6a14-11e7-862a-606c9edc96c3.png>
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#3023>, or mute the thread
<https://github.com/notifications/unsubscribe-auth/AATi5JHKkkYNeiOUfLH0k1y-dGgSPUYcks5sPHMbgaJpZM4ObCg5>
.
|
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. 😇 |
Drop-in replacements are listed at https://github.com/eclipse/eclipse-collections/blob/master/docs/guide.md#-basic-collection-types |
We are currently trying to focus on other things. 🔥 |
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?
The text was updated successfully, but these errors were encountered: