> On Nov 6, 2017, at 5:29 PM, Kelvin Ma via swift-evolution > <[email protected]> wrote: > > hot take: i use the second one a lot but only because i always forget the > first one exists. So I type the = nil just to “be sure”. >
Same here! I just changed a bunch of code since I’d forgotten they were the same > On Mon, Nov 6, 2017 at 4:33 PM, Slava Pestov via swift-evolution > <[email protected] <mailto:[email protected]>> wrote: > Hi all, > > Right now, the following two declarations are equivalent: > > struct S { > var x: Int? > } > > struct S { > var x: Int? = nil > } > > That is, mutable bindings of sugared optional type (but not Optional<T>!) > always have a default value of ‘nil’. This feature increases the surface area > of the language for no good reason, and I would like to deprecate it in > -swift-version 5 with a short proposal. Does anyone feel strongly about > giving it up? I suspect most Swift users don’t even know it exists. > > Slava > _______________________________________________ > swift-evolution mailing list > [email protected] <mailto:[email protected]> > https://lists.swift.org/mailman/listinfo/swift-evolution > <https://lists.swift.org/mailman/listinfo/swift-evolution> > > _______________________________________________ > swift-evolution mailing list > [email protected] > https://lists.swift.org/mailman/listinfo/swift-evolution
_______________________________________________ swift-evolution mailing list [email protected] https://lists.swift.org/mailman/listinfo/swift-evolution
