> On Sep 13, 2016, at 3:13 PM, Hooman Mehr <hoo...@mac.com> wrote:
>
> I guess the reason this is happening is some attempt at backward
> compatibility, but this is clearly causing a serious bug. Have you reported
> it?
No; I’m not a Swift expert, and am not following the 3.0 transition closely
enough to tell whether this is a bug or just some unfortunate but intentional
fallout from the transition.
—Jens
_______________________________________________
swift-users mailing list
swift-users@swift.org
https://lists.swift.org/mailman/listinfo/swift-users
