<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=""><div class="">I know how frustrating it is to throw ideas out and not hear back. So here's my answer: I don't love this either. </div><div class="">I think you're trying to fix something that is fundamentally not only <i class="">not broken</i> but pretty solid as it is currently deployed.</div><div class=""><br class=""></div><div class="">-- Erica</div><div class=""><br class=""></div><div><blockquote type="cite" class=""><div class="">On Jan 29, 2016, at 6:41 AM, Amir Michail <<a href="mailto:a.michail@me.com" class="">a.michail@me.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 Jan 29, 2016, at 5:03 AM, Thorsten Seitz <<a href="mailto:tseitz42@icloud.com" class="">tseitz42@icloud.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div class=""><div class="">I agree with Erica. The ?? operator is very readable IMO.<br class=""></div><div class=""><br data-mce-bogus="1" class=""></div><div class="">Furthermore x?(false).isEmpty looks like it would evaluate false.isEmpty when x is nil which is certainly not what is intended.<br data-mce-bogus="1" class=""></div></div></div></blockquote><div class=""><br class=""></div><div class="">What about this then: ??(false, x?.isEmpty)</div><br class=""><blockquote type="cite" class=""><div class=""><div class=""><div class="">In addition it would not be clear which default should be used in case of multiple optional chainings happening, i.e. what should be the result of person?(false).address?.(true).isEmpty<br data-mce-bogus="1" class=""></div><div class=""><br data-mce-bogus="1" class=""></div><div class="">-Thorsten</div><div class=""><br data-mce-bogus="1" class=""></div><div class=""><br class="">Am 26. Januar 2016 um 03:29 schrieb Erica Sadun via swift-evolution <<a href="mailto:swift-evolution@swift.org" class="">swift-evolution@swift.org</a>>:<br class=""><br class=""><div class=""><blockquote type="cite" class=""><div class="msg-quote"><div class="_stretch"><span class="body-text-content">Not loving this. I'm quite happy with ??-coalescing and don't see<br class="">a compelling reason it needs to be "cleaner". I find your suggested<br class="">enhancement less readable. Looks like an optional chaining across <br class="">a function.<br class=""><br class="">-- E<br class=""><br class=""><blockquote type="cite" class="quoted-plain-text">On Jan 25, 2016, at 7:03 PM, Amir Michail via swift-evolution <<a href="mailto:swift-evolution@swift.org" class="">swift-evolution@swift.org</a>> wrote:</blockquote><blockquote type="cite" class="quoted-plain-text"><br class=""></blockquote><blockquote type="cite" class="quoted-plain-text">Examples:</blockquote><blockquote type="cite" class="quoted-plain-text"><br class=""></blockquote><blockquote type="cite" class="quoted-plain-text">* instead of x ?? false, you would have x?(false)</blockquote><blockquote type="cite" class="quoted-plain-text">* instead of x?.isEmpty ?? false, you would have x?(false).isEmpty</blockquote><blockquote type="cite" class="quoted-plain-text"><br class=""></blockquote><blockquote type="cite" class="quoted-plain-text">I think this change would result in cleaner looking code.</blockquote><blockquote type="cite" class="quoted-plain-text"><br class=""></blockquote><blockquote type="cite" class="quoted-plain-text"><br class=""></blockquote><blockquote type="cite" class="quoted-plain-text">_______________________________________________</blockquote><blockquote type="cite" class="quoted-plain-text">swift-evolution mailing list</blockquote><blockquote type="cite" class="quoted-plain-text"><a href="mailto:swift-evolution@swift.org" data-mce-href="mailto:swift-evolution@swift.org" class="">swift-evolution@swift.org</a><br data-mce-bogus="1" class=""></blockquote><blockquote type="cite" class="quoted-plain-text"><a href="https://lists.swift.org/mailman/listinfo/swift-evolution" data-mce-href="https://lists.swift.org/mailman/listinfo/swift-evolution" class="">https://lists.swift.org/mailman/listinfo/swift-evolution</a><br data-mce-bogus="1" class=""></blockquote><br class="">_______________________________________________<br class="">swift-evolution mailing list<br class=""><a href="mailto:swift-evolution@swift.org" data-mce-href="mailto:swift-evolution@swift.org" class="">swift-evolution@swift.org</a><br class=""><a href="https://lists.swift.org/mailman/listinfo/swift-evolution" data-mce-href="https://lists.swift.org/mailman/listinfo/swift-evolution" class="">https://lists.swift.org/mailman/listinfo/swift-evolution</a><br class=""></span></div></div></blockquote></div></div></div></div></blockquote></div><br class=""></div></div></blockquote></div><br class=""></body></html>