<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 Dec 16, 2015, at 10:44 PM, Chris Lattner <<a href="mailto:clattner@apple.com" class="">clattner@apple.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="">+Doug for his thoughts on the web page:<div class=""><br class=""><div class=""><blockquote type="cite" class=""><div class="">On Dec 16, 2015, at 10:01 PM, J. Cheyo Jimenez <<a href="mailto:cheyo@masters3d.com" class="">cheyo@masters3d.com</a>> wrote:</div></blockquote><div class=""><div class=""><div class=""><blockquote type="cite" class=""><div class="">Should there be a spot on the website or github with frequent proposed changes that are not feasible or that not better solution has been found (such as the ?: operator )?</div></blockquote></div></div></div><div class=""><blockquote type="cite" class=""><div class="">I am thinking this would cut down on people asking to turn operators into keywords (or similar ) but still encourage better solutions to be proposed. </div></blockquote></div><div class=""><br class=""></div><div class="">I think it is a really interesting idea to have a list of “commonly proposed changes” on the Swift evolution web page, with a link to the discussion archives for it. While it shouldn’t be verboten to explore an area in the future, anyone doing so can reasonably be expected to read the previous discussions and only reopen it if there is new information or a new idea.</div><div class=""><br class=""></div><div class="">What do you think Doug?</div></div></div></div></div></blockquote><br class=""></div><div>I think it’s a good idea, which we can incorporate in the swift-evolution repository. My main concern is that I (personally), and the core team in general, probably won’t be able to proactively maintain such a list. We’d happily accept pull requests to help keep the list up-to-date and (as it grows longer) give it some organization.</div><div><br class=""></div><div><span class="Apple-tab-span" style="white-space:pre"> </span>- Doug</div><div><br class=""></div><br class=""></body></html>