<div dir="ltr">In short yes, submit a PR, there's some documentation that deals with this:<div><br><a href="https://github.com/apple/swift-evolution/blob/master/process.md#how-to-propose-a-change">How to propose a change</a></div><div><br></div><div>It may be worthwhile mentioning the PR number in this thread, and likewise ensuring that your PR's description is a good brief summary linking back to this thread.</div><div><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Sun, Mar 20, 2016 at 12:18 AM, Victor Gao via swift-evolution <span dir="ltr"><<a href="mailto:swift-evolution@swift.org" target="_blank">swift-evolution@swift.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word">Do I need to create a md file in the swift evolution repository to post my proposal?<span class=""><div><br><div><blockquote type="cite"><div>On Mar 19, 2016, at 00:12, Jordan Rose <<a href="mailto:jordan_rose@apple.com" target="_blank">jordan_rose@apple.com</a>> wrote:</div><br><div><div style="word-wrap:break-word"><div>[+swift-evolution] Sure! It's just a fancy word for doing something like this:</div><div><br></div><blockquote style="margin:0 0 0 40px;border:none;padding:0px"><div>protocol SelfAppendable {</div><div> init()</div><div> func +=(other: Self)</div><div>}</div><div><br></div><div>func *<Sequence: SelfAppendable >(sequence: Sequence, count: Int) -> Sequence {</div><div> var result = Sequence()</div><div> for _ in 0..<count {</div><div> result += sequence</div><div> }</div><div> return result</div><div>}</div><div><br></div><div><div>extension Array: SelfAppendable {}</div><div>extension String: SelfAppendable {}</div></div></blockquote><div><br></div>Both Array and String already have no-argument initializers and a += function, but they come from the standard library and don't (necessarily) satisfy any protocols, so they wouldn't be declared "implement". I can think of a few different ways to deal with this, but mostly I just want to make sure you (and everyone else) are considering this use case in your proposal. :-)<div><div><br></div><div>Best,</div><div>Jordan<br><br><div><blockquote type="cite"><div>On Mar 18, 2016, at 17:04 , Victor Gao <<a href="mailto:victorgao44@gmail.com" target="_blank">victorgao44@gmail.com</a>> wrote:</div><br><div><div style="word-wrap:break-word">Hi Jordan,<div><br></div><div>Could you explain more of what retroactive modeling is and how it affects the proposal? I am unfamiliar with retroactive modeling. Thanks!</div><div><br></div><div>Victor Gao.</div></div></div></blockquote></div><br></div></div></div></div></blockquote></div><br></div></span></div><br>_______________________________________________<br>
swift-evolution mailing list<br>
<a href="mailto:swift-evolution@swift.org">swift-evolution@swift.org</a><br>
<a href="https://lists.swift.org/mailman/listinfo/swift-evolution" rel="noreferrer" target="_blank">https://lists.swift.org/mailman/listinfo/swift-evolution</a><br>
<br></blockquote></div><br></div>