Infinite recursion between Absolute.range and Absolute.approximateMidPoint

[AverageHelper]

The Absolute.approximateMidPoint and Absolute.range getters seem to call each other. I'm running an app which corroborates this.

In Time/5. Absolute Values/Absolute.swift:

public var range: Range<Instant> {
    let date = approximateMidPoint.date  <--
    ...
}

And in Time/5. Absolute Values/Absolute+Internal.swift:

...
internal var approximateMidPoint: Instant {
    let r = self.range  <--
    ...
}

One simply has to call Absolute(...).range to get a hang and then a crash.

The implementations of these seem to make sense when considered independent of each other, but the fact that they depend on each other recursively is an issue.

I'm not enough of an expert yet on working with Foundation.Date or Time to know quite what to do to split these, but I can at least cobble together some test cases to demonstrate it.

[davedelong]

Yep, this is a dupe of #19 and is fixed on the master branch.

[AverageHelper]

Ah, that works then. Thank you!