<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></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 Jun 11, 2017, at 3:41 PM, Haravikk 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=""><meta http-equiv="Content-Type" content="text/html charset=us-ascii" class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><br class=""><div class=""><blockquote type="cite" class=""><div class="">On 11 Jun 2017, at 22:13, Gor Gyolchanyan 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=""><meta http-equiv="Content-Type" content="text/html charset=utf-8" class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">I agree, this makes focusing on the right types of changes much easier and helps us avoid turning Swift into an incoherent conglomeration of random use-cases (*cough*, C#, *cough*).<div class=""><div class="">Now, the question is: when will be the time to officially push the factory initializers proposal and which stage should it be targeting?</div></div></div></div></blockquote><br class=""></div><div class="">I think there's definitely a need for greater clarity; we could really do with better announcements on the list itself as to when the new phase begins and <b class="">exactly</b> what is in-scope, it also needs to be put more clearly on the swift-evolution repository.</div><div class=""><br class=""></div><div class="">Thing is; people are going to have ideas when they have them, and want to discuss them right away. I've been caught out numerous times with proposals that are almost immediately rejected as out of scope, and still have no idea when I'm supposed to resubmit them.</div><div class=""><br class=""></div><div class=""><b class="">To be honest it's demoralising, as I find myself apathetic towards my own ideas as I have no idea when to revisit them, and by the time I do I've largely lost interest and moved on to other things.</b></div></div>_______________________________________________<br class=""></div></blockquote><br class=""></div><div>This.</div><div><br class=""></div><div>I am sitting on a number of ideas that I think have merit (in a non-random use-case non-C# way) and I have no idea when the right time will be to bring them up. Several were marked as "bring forward to Swift 4" and obvious that was never going to happen for them.</div><div><br class=""></div><div>I think having a queue to submit "proposals for eventually", written when the inspiration is there, and having a core team review (say once a month or even once a quarter) of their viability for future Swift directions would be amazingly valuable.</div><div><br class=""></div><div>An example: <a href="https://github.com/apple/swift-evolution/pull/369" class="">https://github.com/apple/swift-evolution/pull/369</a></div><div><br class=""></div><div>-- E</div><div><br class=""></div></body></html>