<html><head><style>body{font-family:Helvetica,Arial;font-size:13px}</style></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><div id="bloop_customfont" style="font-family:Helvetica,Arial;font-size:13px; color: rgba(0,0,0,1.0); margin: 0px; line-height: auto;">Same here, but I wouldn’t care much if it were gone.</div> <br> <div id="bloop_sign_1510087959354830080" class="bloop_sign"></div> <br><p class="airmail_on">Am 7. November 2017 um 21:40:56, David Hart via swift-evolution (<a href="mailto:swift-evolution@swift.org">swift-evolution@swift.org</a>) schrieb:</p> <blockquote type="cite" class="clean_bq"><span><div><div></div><div>Yeah, I use the first form constantly.<br><br>> On 6 Nov 2017, at 23:33, Slava Pestov via swift-evolution <swift-evolution@swift.org> wrote:<br>> <br>> Hi all,<br>> <br>> Right now, the following two declarations are equivalent:<br>> <br>> struct S {<br>> var x: Int?<br>> }<br>> <br>> struct S {<br>> var x: Int? = nil<br>> }<br>> <br>> 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.<br>> <br>> Slava<br>> _______________________________________________<br>> swift-evolution mailing list<br>> swift-evolution@swift.org<br>> https://lists.swift.org/mailman/listinfo/swift-evolution<br><br>_______________________________________________<br>swift-evolution mailing list<br>swift-evolution@swift.org<br>https://lists.swift.org/mailman/listinfo/swift-evolution<br></div></div></span></blockquote></body></html>