> On Mar 17, 2016, at 9:08 PM, Chris Lattner via swift-evolution > <[email protected]> wrote: > > On Mar 17, 2016, at 5:50 PM, Brent Royal-Gordon <[email protected]> > wrote: > >>> It seems like this unnecessarily complicates the surface model of Swift. >>> To me, it seems like there is no advantage to having two ways to spell this. >> >> @autounwrapped let foo = functionReturningOptional() >> >> I *believe* that, without the `@autounwrapped` attribute, there's no way to >> go from T? to T! without actually restating T somewhere. > > Right, that's part of the feature :-)
Sorry, less snarky answer: You are right that today it is a regression vs: let foo : ImplicitlyUnwrappedOptional = ... However, I have never seen someone actually do that, and if they did, I would observe that the T is a lot more illuminating than the ! part of the type. Is there a concrete use case you are concerned about? -Chris _______________________________________________ swift-evolution mailing list [email protected] https://lists.swift.org/mailman/listinfo/swift-evolution
