TestClock.sleep(until deadline:) suspends when called with a deadline that is equal to TestClock.now about swift-clocks HOT 3 CLOSED

Fixed by #22.

from swift-clocks.

@stephencelis I saw this was reverted: #26
but the revert doesn't provide a rationale. Doesn't reverted-to behaviour break the contract
of https://developer.apple.com/documentation/swift/task/sleep(until:tolerance:clock:), which is supposed to wake up at the deadline?

from swift-clocks.

@bobergj Sorry for not describing the problem, but the change broke existing test clock tests and made TestClock behave differently than other test clocks and schedulers out there, including our combine-schedulers test scheduler, as well as the test schedulers that come with RxSwift, ReactiveSwift, and more.

A clock should suspend when told to sleep, and should only resume when the test clock advances. We do not believe this behavior breaks the contract because the test clock does wake up at the deadline, it just needs to advance first, which is typically done by calling clock.advance() (which is an alias to clock.advance(by: .seconds(0))).

from swift-clocks.