<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div>+1 from me as well, supporting conditional compilation when the two versions of foundation differ and may differ for the foreseeable future seems a must on this end.<br><br>Sent from my iPhone</div><div><br>On 3 Jan 2016, at 10:12, Drew Crawford via swift-evolution <<a href="mailto:swift-evolution@swift.org">swift-evolution@swift.org</a>> wrote:<br><br></div><blockquote type="cite"><div><meta http-equiv="Content-Type" content="text/html charset=utf-8"><blockquote type="cite" class=""><div class="" style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><div class="">If we are going to support something like this, I’d rather see it be something everyone could leverage as there are many use cases for this feature:</div><div class=""><br class=""></div><blockquote class="" style="margin: 0px 0px 0px 40px; border: none; padding: 0px;"><div class=""><font face="Menlo" class="">#if available("package-name", "1.2.*")</font></div><div class=""><font face="Menlo" class="">#endif</font></div></blockquote></div></blockquote><div class=""><br class=""></div>Big +1.<div class=""><br class=""></div><div class="">I've asked specifically to get some kind of <a href="https://lists.swift.org/pipermail/swift-corelibs-dev/Week-of-Mon-20151228/000287.html" class="">conditional compilation on corelibs-foundation</a> being used. corelibs-founcation is currently incompatible with Darwin Foundation, and so it is impractical to make a single codebase build for both.</div><div class=""><br class=""></div><div class="">But building the same application against both Foundations and spotting differences is one of the important ways we're going to spot bugs.</div><div class=""><br class=""></div><div class="">So I think the code quality of Foundation ultimately hinges on getting some feature like this in the language.</div>
<img src="https://u2002410.ct.sendgrid.net/wf/open?upn=dXNHRXbGTqqssqDI7Hn7KyogJzdRthQdFNkQ7LxhQVOhjE-2Bu29Neqw-2BlINtEcopvcvy7tsqm0TE9PmMKnH85b6yAwI9-2Bj-2BTJgb7eqkNEkiBQLf8DGDvTZRXp7BAD2f3EDRTxyN6xCZE3CrZf08pRgyT8S2L-2F9Pco3-2F64w6DAqZ9cj1TCDvKKS6WHjH0BctuA6Mb7Fh-2Fa7NL5WQAKZqj3KaJu98kHF42-2FQ-2FRzdT2JxWQ-3D" alt="" width="1" height="1" border="0" style="height:1px !important;width:1px !important;border-width:0 !important;margin-top:0 !important;margin-bottom:0 !important;margin-right:0 !important;margin-left:0 !important;padding-top:0 !important;padding-bottom:0 !important;padding-right:0 !important;padding-left:0 !important;">
</div></blockquote><blockquote type="cite"><div><span>_______________________________________________</span><br><span>swift-evolution mailing list</span><br><span><a href="mailto:swift-evolution@swift.org">swift-evolution@swift.org</a></span><br><span><a href="https://lists.swift.org/mailman/listinfo/swift-evolution">https://lists.swift.org/mailman/listinfo/swift-evolution</a></span><br></div></blockquote></body></html>