I found a another implementation of this method, and it's simpler to read as a developer. It uses a different built in Java Object which may bring other implications, but it works just fine for it's purpose.
This PR can be accepted or rejected, and it shouldn't make much of a difference to the end user. If this branch becomes outdated, it would seem more prudent to rebase this on top of the new changes rather than creating a merge commit.
The change is pretty straight forward.
I found a another implementation of this method, and it's simpler to read as a developer. It uses a different built in Java Object which may bring other implications, but it works just fine for it's purpose.
This PR can be accepted or rejected, and it shouldn't make much of a difference to the end user. If this branch becomes outdated, it would seem more prudent to rebase this on top of the new changes rather than creating a merge commit.