Dave DeLong

These are great points. I'll think about the proper way to solve this. I'm thinking it might involve falling back to a dateComponents → date approach.

I was thinking about this a bit more. The current behavior is _technically_ correct, and the confusion is arising from a bad API name (and please LMK if you disagree)....

My current thinking on the names are `today.convertingTimeRange(to: ...)` and `today.convertingComponents(to: ...)`

From what I can tell, the problem has to do with the implementation of `NSSecureCoding`; while unarchiving, the code is listing allowed classes, but that doesn't match what's actually encoded...

@petea @philet I'm not using this project anymore and am intending to delete my fork just to keep my personal GitHub tidy. You're welcome to copy the diff and re-apply...

I think the solution here is to compute _two_ differences: ```swift let diff = start - end // hour: 1 minute: 3 let minuteDiff = start.differenceInWholeMinutes(to: end) // minute: 63...

There's an `Examples` folder with an Xcode project with a couple small samples now. I'll close this as completed, and we can open new issues for specific desired examples.

Hi @trispo! The method you're looking for in 1.0 is called [`Fixed.differenceInWholeMinutes(to:)`](https://swiftpackageindex.com/davedelong/time/1.0.0/documentation/time/fixed/differenceinwholeminutes(to:)). That will give you a difference between two fixed values that is _only_ in minutes.

I'm going to reject this for now, since it would involve exposing internal types, and I'm not convinced the demand exists for this functionality. We can absolutely re-evaluate this as...

I believe I've addressed this in the latest code, here: https://github.com/davedelong/time/blob/main/Sources/Time/4-Fixed%20Values/Fixed%2BConversion.swift#L40 There are targeted methods for converting ~Absolute~ Fixed values, based on their granularity. For the most flexibility, there's also...