The ArraySet implementation isn't as optimal as it should be. It passes the tests and works fine otherwise, but some functions do not return expected results, though these are usually less used implementations. (SubSet/HeadSet/TailSet)
A whole refactor of that class has to be made to fix foundation issues with the implementation and to setup a rulesheet how a implementation should work.
Known issues:
SubSet size could be 1 element larger then expected.
ToArray could be a array copy implementation instead of the default AbstractImplementation.
SubSet toArray implementation only copies half of the elements and the other half is not included.
The ArraySet implementation isn't as optimal as it should be. It passes the tests and works fine otherwise, but some functions do not return expected results, though these are usually less used implementations. (SubSet/HeadSet/TailSet)
A whole refactor of that class has to be made to fix foundation issues with the implementation and to setup a rulesheet how a implementation should work.
Known issues:
- [x] SubSet size could be 1 element larger then expected.
- [x] ToArray could be a array copy implementation instead of the default AbstractImplementation.
- [x] SubSet toArray implementation only copies half of the elements and the other half is not included.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
The ArraySet implementation isn't as optimal as it should be. It passes the tests and works fine otherwise, but some functions do not return expected results, though these are usually less used implementations. (SubSet/HeadSet/TailSet)
A whole refactor of that class has to be made to fix foundation issues with the implementation and to setup a rulesheet how a implementation should work.
Known issues: