<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><blockquote type="cite" class=""><div class="">On May 11, 2017, at 1:45 AM, Nicholas Maccharoli via swift-evolution &lt;<a href="mailto:swift-evolution@swift.org" class="">swift-evolution@swift.org</a>&gt; wrote:</div><div class=""><div dir="ltr" class=""><div class="gmail_default" style="font-family:comic sans ms,sans-serif;color:#274e13">I also strongly agree.&nbsp;</div><div class="gmail_default" style="font-family:comic sans ms,sans-serif;color:#274e13"><br class=""></div><div class="gmail_default" style="font-family:comic sans ms,sans-serif;color:#274e13">I can think of no strong argument against this, was this intentional at one point or a compiler bug?<br class=""></div></div></div></blockquote><div><br class=""></div>The language design of #if is more complex than it is in C: it is part of the language grammar, not a separate phase of pre-processing, and must be specifically supported in every position it appears.</div><div><br class=""></div><div>That said, I agree with Chris and Jordan that supporting #if in any simple, sequential position in the grammar is an obvious extension of the existing design and can reasonably be fast-tracked.</div><div><br class=""></div><div>Grammatically similar positions where it's hard to dispute the consistency argument for #if: get-set clauses, precedencegroup declarations.</div><div><br class=""></div><div>A position which would definitely be more useful to prioritize but where both the language design and the implementation are trickier: attribute lists.</div><div><br class=""></div><div>John.</div><div><br class=""><blockquote type="cite" class=""><div class=""><div dir="ltr" class=""><div class="gmail_default" style="font-family:comic sans ms,sans-serif;color:#274e13"><br class=""></div><div class="gmail_default" style="font-family:comic sans ms,sans-serif;color:#274e13">- Nick&nbsp;</div><div class="gmail_default" style="font-family:comic sans ms,sans-serif;color:#274e13"><br class=""></div></div><div class="gmail_extra"><br class=""><div class="gmail_quote">On Thu, May 11, 2017 at 2:37 PM, Chris Lattner via swift-evolution <span dir="ltr" class="">&lt;<a href="mailto:swift-evolution@swift.org" target="_blank" class="">swift-evolution@swift.org</a>&gt;</span> wrote:<br class=""><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word" class="">I agree with Jordan.<div class=""><br class=""></div><div class="">-Chris</div><div class=""><br class=""><div class=""><blockquote type="cite" class=""><div class=""><div class="h5"><div class="">On May 10, 2017, at 11:47 AM, Jordan Rose via swift-evolution &lt;<a href="mailto:swift-evolution@swift.org" target="_blank" class="">swift-evolution@swift.org</a>&gt; wrote:</div><br class="m_3026747317112192948Apple-interchange-newline"></div></div><div class=""><div class=""><div class="h5"><div style="word-wrap:break-word" class=""><div class="">I'm in favor, certainly. I'd personally say this wouldn't even need to go through the full evolution process, but I'm not a core team member.</div><div class=""><br class=""></div><div class="">Jordan</div><div class=""><br class=""></div><br class=""><div class=""><blockquote type="cite" class=""><div class="">On May 10, 2017, at 01:32, rintaro ishizaki via swift-evolution &lt;<a href="mailto:swift-evolution@swift.org" target="_blank" class="">swift-evolution@swift.org</a>&gt; wrote:</div><br class="m_3026747317112192948Apple-interchange-newline"><div class=""><div dir="ltr" class="">Hi evolution community,<div class=""><br class=""></div><div class="">This proposal allows you to enclose switch cases with #if directive.<br class=""></div><div class="">Implementation: <a href="https://github.com/apple/swift/pull/9457" target="_blank" class="">https://github.com/apple/<wbr class="">swift/pull/9457</a></div><div class="">This is one of the oldest SR issue:</div><div class=""><a href="https://bugs.swift.org/browse/SR-2" target="_blank" class="">https://bugs.swift.org/browse/<wbr class="">SR-2</a></div><div class=""><a href="https://bugs.swift.org/browse/SR-4196" target="_blank" class="">https://bugs.swift.org/browse/<wbr class="">SR-4196</a></div><div class=""><br class=""></div><div class="">Thanks!</div><div class="">Rintaro</div></div></div></blockquote></div><br class=""></div></div></div><span class="">______________________________<wbr class="">_________________<br class="">swift-evolution mailing list<br class=""><a href="mailto:swift-evolution@swift.org" target="_blank" class="">swift-evolution@swift.org</a><br class=""><a href="https://lists.swift.org/mailman/listinfo/swift-evolution" target="_blank" class="">https://lists.swift.org/<wbr class="">mailman/listinfo/swift-<wbr class="">evolution</a><br class=""></span></div></blockquote></div><br class=""></div></div><br class="">______________________________<wbr class="">_________________<br class="">
swift-evolution mailing list<br class="">
<a href="mailto:swift-evolution@swift.org" class="">swift-evolution@swift.org</a><br class="">
<a href="https://lists.swift.org/mailman/listinfo/swift-evolution" rel="noreferrer" target="_blank" class="">https://lists.swift.org/<wbr class="">mailman/listinfo/swift-<wbr class="">evolution</a><br class="">
<br class=""></blockquote></div><br class=""></div>
_______________________________________________<br class="">swift-evolution mailing list<br class=""><a href="mailto:swift-evolution@swift.org" class="">swift-evolution@swift.org</a><br class="">https://lists.swift.org/mailman/listinfo/swift-evolution<br class=""></div></blockquote></div><br class=""></body></html>