jgcaruso

I love that its so easy to create Extensions in #swift so adding your own when necessary isn't a huge deal, but why doesn't this already exist in TimeInterval? Or did I miss something obvious 😅

```
extension TimeInterval {
static var Hour: TimeInterval {
get {
TimeInterval(60 * 60)
}
}

static var Day: TimeInterval {
get {
.Hour * 24
}
}
}
```

Feb 3, 2023 at 5:37pmWeb
Show threadEric BlairFeb 3, 2023
@jgcaruso well, that isn’t always true… https://yourcalendricalfallacyis.com
Your Calendrical Fallacy Is...

Show threadOle BegemannFeb 5, 2023
@jgcaruso Adding to what others have said, TimeInterval is just a typealias for Double, so extending TimeInterval really extends Double. I wouldn’t want a Double.hour API.
Show threadjgcarusoFeb 5, 2023

@ole oh good point! I didn't realize TimeInterval was just a typealias. Yeah just tried it out and it's weird having `Double.Hour` be an option... but it's also nice being able to just type `.Hour` when a TimeInterval is needed

Probably fine for this little project I'm playing with but something I'll think twice about on something larger.

Show threadOle BegemannFeb 5, 2023
@jgcaruso Long term, the new Duration type in Swift is probably a better choice than TimeInterval. It seems more targeted at very small intervals (seconds and below), but I don’t see a reason why it couldn’t be used for calendrical calculations as well. It’s twice as big as a Double, but I don’t think that’s a deal breaker. Either way, it’ll take time for APIs to adopt it. https://developer.apple.com/documentation/swift/duration
Duration | Apple Developer Documentation

A representation of high precision time.

Apple Developer Documentation