eclipse-collections
eclipse-collections copied to clipboard
Add missing methods to ImmutableMapFactory
Additional changes include -
- Replace usage of newly deprecated methods.
- Update interface Javadoc to align with deprecated implementation in (ImmutableMapFactoryImpl#ofMap).
Closes gh-738
Signed-off-by: Kedar Joshi [email protected]
I think I should also add @Since
on new methods. Right ?
@kedar-joshi thanks for your contribution! Before I review the PR, a little bit of admin stuff so that it is easier for me when I write the release notes. Can you break the additional changes which you have done in separate commits, please? It is fine to have it in this PR, just separate commits, so that I can look at the history easily and compile the release notes. Also, the history remains clean.
Yes, please add since
tag as well.
Please ping me when it is done, I will review it. Cheers!
Thanks for helping us out!
Can you break the additional changes which you have ..
Sure.
There are build failures. Also the implementation is far easier than what you have right now. Please take a look in the review. Thanks for your contribution!
Looping in @donraab as he initially opened the issue.
I see the context of gh-738 now, but the deprecation still doesn't make sense as written. The methods with bad generics are deprecated, but the new methods also have bad generics. There's no version of ofMap that's not deprecated.
I think we should experiment with pulling methods up to a super-interface to drive consistency (in a separate commit) to make this sort of thing enforced by the compiler.
Here's an example, to start the conversation: https://github.com/motlin/eclipse-collections/commit/f9397b23d0f2876dce1d184540a5bc1e3a378333
And here's a similar example for Maps. This one doesn't compile because the interfaces are truly not compatible. https://github.com/motlin/eclipse-collections/commit/07c81aad52e4f9fb797f5e9a804fac0773447314
is this pull request abadoned?