[swift-users] Flatmap initializer inconsistency

[Saagar Jha]

Well, the question still remains about why the compiler chose init(exactly:) over init(). Shouldn’t there at least a warning of ambiguity?

Saagar Jha

> On May 1, 2017, at 12:11, Zhao Xin via swift-users <swift-users at swift.org> wrote:
> 
> In my test, compiler thought you use `init?(exactly value: Double <>)`, which returns nil. So this is not a bug.
> 
> Zhaoxin
> 
> On Tue, May 2, 2017 at 1:39 AM, Halen Wooten via swift-users <swift-users at swift.org <mailto:swift-users at swift.org>> wrote:
> Hi,
> 
> I'm seeing a weird issue with using an initializer in flatMap. Here's
> an example:
> 
> ```
> let time: TimeInterval? = 662.82582598600004
> let intTimeFlatmap = time.flatMap(Int.init) // nil
> let intTime = Int(time!) // 662
> ```
> 
> I would expect for the flatMap call to return an optional Int with the
> proper value of 662. Is there something I'm misunderstanding, or is
> this a swift bug?
> 
> Thanks,
> Halen
> _______________________________________________
> swift-users mailing list
> swift-users at swift.org <mailto:swift-users at swift.org>
> https://lists.swift.org/mailman/listinfo/swift-users <https://lists.swift.org/mailman/listinfo/swift-users>
> 
> _______________________________________________
> swift-users mailing list
> swift-users at swift.org
> https://lists.swift.org/mailman/listinfo/swift-users

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.swift.org/pipermail/swift-users/attachments/20170501/bfbb0d08/attachment.html>