PrePitch: Optional variables should require explicit initialization

[masters3d]

I missed this other one too.

Pitch: Remove default initialization of optional bindings

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. S…

I’m leaning towards proposing something along the lines of default initialization via property wrappers.

@Default var foo:String // initialized to “”
@Default var foo2: String? // initialized to .some(String())