<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="">OK, so Optional conversions need to be re-evaluated, but what about passing a flag disabling all implicit conversions entirely?<div class=""><br class=""><div><blockquote type="cite" class=""><div class="">On Dec 9, 2015, at 5:47 PM, Chris Lattner <<a href="mailto:clattner@apple.com" class="">clattner@apple.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><meta http-equiv="Content-Type" content="text/html charset=us-ascii" class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><br class=""><div class=""><blockquote type="cite" class=""><div class="">On Dec 9, 2015, at 11:20 AM, Developer via swift-evolution <<a href="mailto:swift-evolution@swift.org" class="">swift-evolution@swift.org</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><meta http-equiv="Content-Type" content="text/html charset=us-ascii" class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">Hello all,<br class=""><br class="">Considering what I do with Swift, I recently posted a pull request that adds a flag to the frontend that would disable all implicit optional conversions by making them errors. From my perspective, implicit conversions are convenient, but they allow certain strange behaviors (<a href="https://github.com/typelift/Swiftz/blob/master/SwiftzTests/EitherSpec.swift#L72" class="">https://github.com/typelift/Swiftz/blob/master/SwiftzTests/EitherSpec.swift#L72</a>) to show up. For the community, the question is threefold:<br class=""><br class="">1) Would anything break if this were applied?<br class="">2) Would it be appropriate to expand the flag by allowing all implicit conversions to be disabled?<br class="">3) If you remain unconvinced it should be an error, would implicit conversion warnings be more appropriate?<br class=""></div></div></blockquote></div><br class=""><div class="">Hi Robert,</div><div class=""><br class=""></div><div class="">The rules for implicit conversions are optionals need to be re-evaluated, I expect this to happen for Swift 3 (after Swift 2.2 is out of the door). Once that is done, we can talk about a proposal like this.</div><div class=""><br class=""></div><div class="">-Chris</div></div></div></blockquote></div><br class=""></div></body></html>