swhitty
Consider whether `ContinousClock` is the "correct" default clock
Task.sleep(nanoseconds:) is used to sleep when calling withThrowingTimeout(seconds:). AFAICT Task.sleep(nanoseconds:) pauses on system sleep.
The withThrowingTimeout(after:) function uses a ContinousClock which is "A clock that measures time that always increments and does not stop incrementing while the system is asleep."
I think the withThrowingTimeout() functions that don't require a Clock parameter should all have the same behavior. Should ContinousClock change to SuspendingClock?
I think this is a very valid suggestion and I agree that consistent behaviour is better here so it should switch to SuspendingClock
Well Task.sleep(for:)'s default clock is .continuous, so it's maybe the right move to match that...
I have asked in the Swift forums regarding why .continuous was chosen as the default, mostly for educational purposes, and perhaps to see if we can get better documentation regarding Task.sleep(nanoseconds:)
https://forums.swift.org/t/why-was-continuousclock-chosen-as-the-default-for-task-sleep-for/81047