Enhance DataSize with comparators and simple algebra

I think it would be useful to add some handy operators to DataSize, like comparators and some algebra:

• DataSize plus(DataSize dataSize)
• DataSize minus(DataSize dataSize)
• DataSize divide(int scalar)
• DataSize multiply(int scalar)
• boolean isGreaterThan(DataSize dataSize)
• boolean isLessThan(DataSize dataSize)
• boolean isEqualTo(DataSize dataSize)
• static DataSize sum(DataSize ...dataSizes)
• static DataSize min(DataSize ...dataSizes)
• static DataSize max(DataSize ...dataSizes)
• static DataSize between(DataSize x, DataSize y)

These comparators are far more readable than using the .compareTo (Similar to Java’s approach with Instant - isBefore and isAfter). Also being able to do some simple algebra will be very handy for when you are doing calculations with sizes (dataSize1.plus(dataSize2) is far more readable than doing DataSize.ofBytes(dataSize1.toBytes() + dataSize2.toBytes()).

[sbrannen]

Hi @nhmarujo,

Thanks for the proposal (and your first issue) for the Spring Framework.

At this time, the team does not wish to add to the public API of DataSize since such additions are not needed within the framework itself.

In light of that, I am closing this issue.

[nhmarujo]

Hi @sbrannen . Thank you for your reply.

I can provide a concrete use case we had recently - we were creating a way to automatically calibrate argon2 parameters. For that we had to try to iteratively find the best memory setting, which involved starting at some given value, do some runs and then calculate next step until some criteria was met. This simple example involved:

• adding/substracting DataSize
• finding middle point between 2 DataSize
• comparing DataSize

I can, however, think of more use cases:

• have several properties to specify how much memory is to be used in each category and then having to sum them all in code
• Define in properties a lower and upper bound and then have in code to find out the range size or a middle point

Of course you can do any of these without the operators I was suggesting, but I reckon they would make the code far easier to implement and much more readable.

Best regards