<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></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 Jan 14, 2017, at 6:46 PM, Xiaodi Wu <<a href="mailto:xiaodi.wu@gmail.com" class="">xiaodi.wu@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class="">On Sat, Jan 14, 2017 at 5:35 PM, Amir Michail <span dir="ltr" class=""><<a href="mailto:a.michail@me.com" target="_blank" class="">a.michail@me.com</a>></span> wrote:<br class=""><div class="gmail_extra"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class=""><br class="">
> On Jan 14, 2017, at 6:28 PM, Xiaodi Wu <<a href="mailto:xiaodi.wu@gmail.com" class="">xiaodi.wu@gmail.com</a>> wrote:<br class="">
><br class="">
> This has been brought up on this list before. The conclusion of the previous thread on this topic was that there is a way to do this:<br class="">
><br class="">
> #if false<br class="">
> // put your code here<br class="">
> #endif<br class="">
><br class="">
<br class="">
</span>This would not check the code for compilability within the surrounding code. This requires more than a syntax check.</blockquote><div class=""><br class=""></div><div class="">I can't say I've ever needed that feature; could you share a concrete use case?</div><div class=""><br class=""></div></div></div></div></div></blockquote><div><br class=""></div><div>Consider an array of levels for a game where some levels are commented out for possible future use. It would be nice to have such level entries continue to compile as the code elsewhere evolves and yet not be included in the executable.</div><br class=""><blockquote type="cite" class=""><div class=""><div dir="ltr" class=""><div class="gmail_extra"><div class="gmail_quote"><div class="">In any case, if you put code in a function that's not exported and never invoked, I believe you would achieve the desired effect. Within the body of a function, you could do so in a closure.</div><div class=""><br class=""></div><div class="">```</div><div class="">func foo() {</div><div class=""> // code you want to run</div><div class=""> _ = {</div><div class=""> // code you don't intend to run</div><div class=""> }</div><div class=""> // more code you want to run</div><div class="">}</div><div class="">```</div><div class=""><br class=""></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="HOEnZb"><div class="h5">
> It does not allow you to comment out fragments of a single statement, but the incremental value of devoting time to additionally support that is, it would seem, low.<br class="">
><br class="">
> On Sat, Jan 14, 2017 at 17:18 Amir Michail via swift-evolution <<a href="mailto:swift-evolution@swift.org" class="">swift-evolution@swift.org</a>> wrote:<br class="">
> The code in a “code comment" must compile (not just be syntactically correct) yet must not have any effect on the resulting executable.<br class="">
><br class="">
> For example, commented entries in an array would be checked for compilability but would not be included in the executable.<br class="">
><br class="">
> Such “code comments" would allow you to have code/data that is currently unused but is constantly checked to be valid just in case you want to use it in the future.<br class="">
><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="">
</div></div></blockquote></div><br class=""></div></div>
</div></blockquote></div><br class=""></body></html>