<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="">Hi David,<div class=""><br class=""><div class="">Thanks for your reply., OK, I think I understand. </div><div class=""><br class=""></div><div class="">It then is a capacity problem, right?</div><div class=""><br class=""></div><div class=""><div class="">In effect, it means restricting people from bringing perhaps very valuable </div><div class="">(not necessarily my contributions) </div><div class="">and essential ideas forward, which could play a crucial role improving Swift.</div></div><div class=""><br class=""></div><div class="">I think this is a very negative aspect. surely bouncing creative people away,</div><div class="">dropping their efforts and interest here altogether. </div><div class=""><br class=""></div><div class="">The question then remains, where / when / how can one bring topics </div><div class="">that are taking a longer stretch and are not bound to a certain release of Swift,</div><div class="">seemingly “outside” of this restriction under attention?</div><div class=""><div class=""><br class=""></div></div><div class="">if swift evolution is (currently? ) not open for new ideas/topics:</div><div class="">I thought that was the primary purpose of Swift evolution?</div><div class=""><br class=""></div><div class="">Kind Regards</div><div class="">Ted</div><div class=""><br class=""></div><div class=""><br class=""><div><blockquote type="cite" class=""><div class="">On 12 Oct 2016, at 21:48, David Hart <<a href="mailto:david@hartbit.com" class="">david@hartbit.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><meta http-equiv="Content-Type" content="text/html charset=utf-8" class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div class="">Hello Ted,</div><div class=""><br class=""></div><div class="">Please try to understand. As Xiaodi and others have said a few times, it has nothing to do with the topic being important or interesting. The current phase of Swift 4’s development does not allow any extensive discussion or review on topics which do not impact ABI stability:</div><div class=""><br class=""></div><div class=""><i class="">Stage 1 focuses on the essentials required for source and ABI stability. Features that don't fundamentally change the ABI of existing language features or imply an ABI-breaking change to the standard library will not be considered in this stage.</i></div><br class=""><div class=""><blockquote type="cite" class=""><div class="">On 12 Oct 2016, at 19:14, Ted F.A. van Gaalen 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=""><div class="" style="font-family: Helvetica; font-size: 14px; font-style: normal; font-variant-caps: 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;">Apart from my perhaps fierce reaction, I am not aware of doing something wrong.</div><div class="" style="font-family: Helvetica; font-size: 14px; font-style: normal; font-variant-caps: 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;">and I still find this topic very important. </div></div></blockquote></div><br class=""><div class="">David.</div></div></div></blockquote></div><br class=""></div></div></body></html>