Re: [swift-evolution] [swift-evolution-announce] [Accepted, pending implementation] SE-0054: Abolish ImplicitlyUnwrappedOptional type

> On Mar 31, 2016, at 2:24 PM, Shawn Erickson via swift-evolution > wrote: > > > > On Thu, Mar 31, 2016 at 9:43 AM Chris Lattner > wrote: > That said, this is the sort of proposal that can have a profound impact on

Re: [swift-evolution] [swift-evolution-announce] [Accepted, pending implementation] SE-0054: Abolish ImplicitlyUnwrappedOptional type

This seems like it would be a useful facility in general - the community may be able to provide audited headers even if the maintainers of the original project have zero interest in merging those changes. That burden is unreasonably high if it requires constant merging of the headers. Russ >

Re: [swift-evolution] [swift-evolution-announce] [Accepted, pending implementation] SE-0054: Abolish ImplicitlyUnwrappedOptional type

On Thu, Mar 31, 2016 at 9:43 AM Chris Lattner wrote: > That said, this is the sort of proposal that can have a profound impact on > the actual experience using unaudited APIs. The core team believes that > the experience will be good, but we would like to get some experience