Hi David,
> On Aug 26, 2017, at 15:36, David Zarzycki wrote:
>
> Without going into details, it looks like the Swift wrappers for
> dispatch_time_t are very, very broken. In short, dispatch_time_t (in the C
> world) is intentionally documented as an opaque type, but the Swift wrappers
> assum
Hi Guillaume,
Without going into details, it looks like the Swift wrappers for
dispatch_time_t are very, very broken. In short, dispatch_time_t (in the C
world) is intentionally documented as an opaque type, but the Swift wrappers
assume otherwise and jump to wrong conclusions about the impleme
On Linux (Ubuntu 16.04) and swift distributions from 3.0.2 to the latest 4.0
snapshot, I’m seeing incorrect behaviour involving DispatchTime.distantFuture:
(also: https://bugs.swift.org/browse/SR-5706)
***
import Dispatch
let now = DispatchTime.now()
let future = DispatchTime.distantFuture
asser
