[swift-evolution] IUO in Swift 3.0

David Hart david at hartbit.com
Wed Jun 29 01:13:19 CDT 2016

Just to close the discussion: have all the bugs pertaining to the incomplete implementation of SE-0054 been tracked? If not, I don’t mind writing them.


> On 22 Jun 2016, at 22:07, Joe Groff via swift-evolution <swift-evolution at swift.org> wrote:
>> On Jun 22, 2016, at 1:03 PM, Chris Lattner <clattner at apple.com> wrote:
>>> On Jun 22, 2016, at 8:56 AM, Joe Groff <jgroff at apple.com> wrote:
>>>> I think that there is some confusion here: it is true that IUO exists internally as a type within the compiler, but the idea of our current implementation is that that is just an implementation detail within the compiler (similar to LValueType, which has no user syntax), not an exposed part of the programmer model.
>>>> That said, the “T!” *syntax* is intended to stay in Swift.  This is the way to model the IUO declaration modifier, as outlined in the proposal.
>>> As implemented in the seed, T! still leaks into the user type system.
>> Are there specific examples of that?  Those examples are bugs, that should be fixed.
>> -Chris
> var x = [Int!]()
> -Joe
> _______________________________________________
> swift-evolution mailing list
> swift-evolution at swift.org <mailto:swift-evolution at swift.org>
> https://lists.swift.org/mailman/listinfo/swift-evolution <https://lists.swift.org/mailman/listinfo/swift-evolution>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.swift.org/pipermail/swift-evolution/attachments/20160629/30e5b33e/attachment.html>

More information about the swift-evolution mailing list