The few utility methods included in AlgorithmUtils were not meant to be exposed outside of the library; they are really "internal" utility methods. For now it doesn't cause any issues, but the implementation and behavior of those methods could be changed in the future and that could break other projects using those methods.
The methods will be moved to a new utility class in the "internal" package, and the ones in AlgorithmUtils will be deprecated.
Note that if one day this library fully (and properly) supports Java modules, the classes in the "internal" package won't be exposed outside of the library anymore...
depryf
commented
5 years ago
The few utility methods included in AlgorithmUtils were not meant to be exposed outside of the library; they are really "internal" utility methods. For now it doesn't cause any issues, but the implementation and behavior of those methods could be changed in the future and that could break other projects using those methods.
The methods will be moved to a new utility class in the "internal" package, and the ones in AlgorithmUtils will be deprecated.
Note that if one day this library fully (and properly) supports Java modules, the classes in the "internal" package won't be exposed outside of the library anymore...