<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><br class=""><div><blockquote type="cite" class=""><div class="">On Mar 24, 2016, at 4:22 AM, Hugues Bernet-Rollande via swift-evolution <<a href="mailto:swift-evolution@swift.org" class="">swift-evolution@swift.org</a>> wrote:</div><div class=""><div class=""><div class=""><div class="">```</div><div class="">var a:String? = String()</div><div class="">// or</div><div class="">var b = String() as String?</div><div class="">// or</div><div class="">var c:Optional<String> = String()<br class=""></div><div class="">```</div></div></div></div></blockquote><br class=""></div><div>When I need to force an optional (primarily for sample code) I can do this already:</div><div><br class=""></div><div>```</div><div><font face="Menlo" class="">var myOptionalString = Optional("")</font></div><div>```</div><div><br class=""></div><div>In this example, `myOptionalString ` picks up the type as well as the optionality.</div><div>Does this not meet your requirement of "<i class="">Allowing to specify only the optionality part of </i></div><div><i class="">a variable type </i><i class="">while still having the actual wrapped type infered by the assignement</i>" in existing</div><div>Swift?</div><div><br class=""></div><div>Beyond that, can you offer any compelling use-cases that motivate this change?</div><div><br class=""></div><div>-- E</div><div><br class=""></div><br class=""></body></html>