<html><body><div><br><div><blockquote type="cite"><div class="msg-quote"><div class="gmail_quote"><div dir="ltr">Em ter, 19 de jan de 2016 às 02:03, Joe Groff via swift-evolution <<a href="mailto:swift-evolution@swift.org" data-mce-href="mailto:swift-evolution@swift.org">swift-evolution@swift.org</a>> escreveu:<br></div><blockquote class="gmail_quote" style="margin: 0 0 0 0.8ex; border-left: 1px #ccc solid; padding-left: 1ex;" data-mce-style="margin: 0 0 0 0.8ex; border-left: 1px #ccc solid; padding-left: 1ex;"><div style="word-wrap: break-word;" data-mce-style="word-wrap: break-word;"><br></div><div style="word-wrap: break-word;" data-mce-style="word-wrap: break-word;"><div>Getting rid of magic is definitely a goal, but I think we want to go in the *opposite* direction. Implicit Optional promotion creates lots of problems, and ImplicitlyUnwrappedOptional's behavior can be hard to predict. We plan to reform the type system around both kinds of Optional soon. <br></div></div><div style="word-wrap: break-word;" data-mce-style="word-wrap: break-word;"><div><br></div><div>-Joe</div></div></blockquote></div></div></blockquote></div><div><span><br data-mce-bogus="1"></span></div><div><span>Hi Joe, can you share already what this reformation will probably look like? </span></div><div><span>Will we have to use .Some(x) instead of just writing x? What about if-let syntax, will this change?<br></span></div><div><span><br data-mce-bogus="1"></span></div><div><span>-Thorsten<br data-mce-bogus="1"></span></div></div></body></html>