You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Something that's quite common in datetime libraries is an 'interval' type.
It's not the question whether such a thing could be implemented, but whether it is possible to define the 'just right' abstraction that supports the common use cases without being overly complex.
Questions that come to mind:
are intervals always closed-open, or are other variants possible?
Can intervals only exist of aware types?
The text was updated successfully, but these errors were encountered:
3.1.1.6 time interval
part of the time axis limited by two instants and, unless otherwise stated, the limiting instants themselves
so it's inclusive-inclusive by default, but it's probably better to specify it yourself because it's not reasonable for someone to expect 12:00/13:00 to be 61 minutes long
Something that's quite common in datetime libraries is an 'interval' type.
It's not the question whether such a thing could be implemented, but whether it is possible to define the 'just right' abstraction that supports the common use cases without being overly complex.
Questions that come to mind:
The text was updated successfully, but these errors were encountered: