[swift-evolution] Pitch: Remove default initialization of optional bindings
David Hart
david at hartbit.com
Tue Nov 7 14:40:42 CST 2017
Yeah, I use the first form constantly.
> On 6 Nov 2017, at 23:33, Slava Pestov via swift-evolution <swift-evolution at swift.org> 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
> swift-evolution at swift.org
> https://lists.swift.org/mailman/listinfo/swift-evolution
More information about the swift-evolution
mailing list