<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div>While that is true, I suspect with the race to a stable language, the plan is to design features as if the language were to stay solid. I wonder about the wisdom in designing part of the language to handle the fact they are not finished designing the language.</div><div id="AppleMailSignature"><br></div><div id="AppleMailSignature">Perhaps as an compromise, they could treat different versions of swift as features in and of themselves?</div><div id="AppleMailSignature"><br></div><div id="AppleMailSignature">- Rod</div><div><br>On 21 Dec 2015, at 7:33 AM, Radosław Pietruszewski 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"><div class="">But the thing is, right now it’s not just new features that show up in new releases. We also have breaking syntax changes.</div><div class=""><br class=""></div><div class="">Feature detection make more sense in the future (perhaps one day we could have an “unstable” Swift branch with experimental features), but right now version detection makes more sense.</div><br class=""><div class="">
<div class="">— Radek</div>
</div>
<br class=""><div><blockquote type="cite" class=""><div class="">On 20 Dec 2015, at 20:28, James Campbell 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=""><span style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display: inline !important;" class="">I think we should be moving towards feature detection over swift version detection</span></div></blockquote></div><br class="">
<img src="https://u2002410.ct.sendgrid.net/wf/open?upn=a745LmqnDfg8U5xkzxO94fzXSZ0ZB2d7MXjmVBHs4IF5-2BFK6DPFe1IXmj0e0-2F82RHxP0U-2FrSXTR03ICiijzM5kKa-2BLw209qN3fZROu1hQKtlRitqf2IE5PsiJrizW-2B9r2b8lRFyR4dn90bRSdRHtsptu8iFFLSluhi-2BVlmkCfrkAboSyB3ffQnJF46QbXpU9oiSuyZbUHgx9MnvtMi292cZqurU783-2FywXJxygk56Xg-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>