<div dir="ltr">I wasn&#39;t explicit about that in the proposal, but I was intending that these should be renamed too. There&#39;s a minor snag: JoinedSequence already exists. I haven&#39;t taken a close look at both implementations yet, but it&#39;s possible we could just combine them.<div class="gmail_extra">
<br><div class="gmail_quote">On Mon, Jul 25, 2016 at 12:46 AM, Charlie Monroe via swift-evolution <span dir="ltr">&lt;<a href="mailto:swift-evolution@swift.org" target="_blank">swift-evolution@swift.org</a>&gt;</span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Shouldn&#39;t the proposal also mention renaming FlattenCollection, FlattenBidirectionalCollection and FlattenSequence to Joined*(Collection|Sequence)? Or are these going to keep their name?<br>
<div class="HOEnZb"><div class="h5"><br>
&gt; On Jul 25, 2016, at 8:10 AM, Chris Lattner via swift-evolution &lt;<a href="mailto:swift-evolution@swift.org">swift-evolution@swift.org</a>&gt; wrote:<br>
&gt;<br>
&gt; Hello Swift community,<br>
&gt;<br>
&gt; The review of &quot;SE-0133: Rename `flatten()` to `joined()`&quot; begins now and runs through July 26.  Apologies for the short review cycle, but we’re right up against the end of source breaking changes for Swift 3.  The proposal is available here:<br>
&gt;<br>
&gt;       <a href="https://github.com/apple/swift-evolution/blob/master/proposals/0133-rename-flatten-to-joined.md" rel="noreferrer" target="_blank">https://github.com/apple/swift-evolution/blob/master/proposals/0133-rename-flatten-to-joined.md</a><br>
&gt;<br>
&gt; Reviews are an important part of the Swift evolution process. All reviews should be sent to the swift-evolution mailing list at<br>
&gt;<br>
&gt;       <a href="https://lists.swift.org/mailman/listinfo/swift-evolution" rel="noreferrer" target="_blank">https://lists.swift.org/mailman/listinfo/swift-evolution</a><br>
&gt;<br>
&gt; or, if you would like to keep your feedback private, directly to the review manager.<br>
&gt;<br>
&gt; What goes into a review?<br>
&gt;<br>
&gt; The goal of the review process is to improve the proposal under review through constructive criticism and contribute to the direction of Swift. When writing your review, here are some questions you might want to answer in your review:<br>
&gt;<br>
&gt;       * What is your evaluation of the proposal?<br>
&gt;       * Is the problem being addressed significant enough to warrant a change to Swift?<br>
&gt;       * Does this proposal fit well with the feel and direction of Swift?<br>
&gt;       * If you have used other languages or libraries with a similar feature, how do you feel that this proposal compares to those?<br>
&gt;       * How much effort did you put into your review? A glance, a quick reading, or an in-depth study?<br>
&gt;<br>
&gt; More information about the Swift evolution process is available at<br>
&gt;<br>
&gt;       <a href="https://github.com/apple/swift-evolution/blob/master/process.md" rel="noreferrer" target="_blank">https://github.com/apple/swift-evolution/blob/master/process.md</a><br>
&gt;<br>
&gt; Thank you,<br>
&gt;<br>
&gt; -Chris Lattner<br>
&gt; Review Manager<br>
&gt; _______________________________________________<br>
&gt; swift-evolution mailing list<br>
&gt; <a href="mailto:swift-evolution@swift.org">swift-evolution@swift.org</a><br>
&gt; <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>
_______________________________________________<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>
</div></div></blockquote></div><br></div></div>