Support for timespans in min(), max(), etc.

[dotGrim]

Suggestion

Allow timespans to be used in number sorting functions (min, max, ceil, floor, etc.)
For functions that involve rounding, either round to the nearest second or round to an optional timespan argument (1 tick, 5 tick, 2 seconds, etc.)

Why?

Timespans often need to be sorted in this manner already. This would just provide ease of use for messing with timespans.
Timespans can already be sorted (sorted indices of {_lst::*} in descending order), so it's not revolutionary.

Other

No response

Agreement

• I have read the guidelines above and affirm I am following them with this suggestion.

[Fusezion]

Just making sure I understand the premises of implementing this, not saying I will currently but may take a look.
the easiest way to implement this would be to check if a comparator exists with supportOrdering as true.

Or would the team prefer is different method of handling this?

[sovdeeth]

Using comparators is great for min/max

I'm not sure how ceil/floor is meant to be handled here, though. What base should it act in? If we ceil 2 minutes, should it be 1 hour or 2 mins? What about 2.5 mins? Or 30.1 mins? It might be better to stick allowing the user to convert to 'minutes of' and round that for these cases.

[Fusezion]

I believe its best to only implement this for min, max and clamp where we have a better basis of it.
I think its best for round, ceil and floor to be handled by the user, As I feel like those cases are mainly for things like 30.1 minutes like you said.

[dotGrim]

Using comparators is great for min/max

I'm not sure how ceil/floor is meant to be handled here, though. What base should it act in? If we ceil 2 minutes, should it be 1 hour or 2 mins? What about 2.5 mins? Or 30.1 mins? It might be better to stick allowing the user to convert to 'minutes of' and round that for these cases.

I initially mentioned rounding rules, how it could be round(13.4 seconds, 10 seconds) = 10 seconds, rounding arg-1 to the nearest arg-2. It wouldn't have as much use case as min/max but it would be nice to have if it's not too difficult to implement.

[sovdeeth]

I suppose that's feasible as long as the input implements both division and multiplication operators. Probably best to have this as 2 pts tho