<div dir="ltr">Excellent. Having one canonical, unambiguous way to get the string representation should make things simpler and easier for developers.<div><br></div><div>Austin</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Thu, May 19, 2016 at 3:57 PM, Dave Abrahams 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"><span class=""><br>
on Tue May 17 2016, Chris Lattner &lt;<a href="mailto:swift-evolution@swift.org">swift-evolution@swift.org</a>&gt; wrote:<br>
<br>
&gt; Hello Swift community,<br>
&gt;<br>
&gt; The review of &quot;SE-0089: Renaming String.init&lt;T&gt;(_: T)&quot; begins now and<br>
&gt; runs through May 23. The proposal is available here:<br>
&gt;<br>
&gt;       <a href="https://github.com/apple/swift-evolution/blob/master/proposals/0089-rename-string-reflection-init.md" rel="noreferrer" target="_blank">https://github.com/apple/swift-evolution/blob/master/proposals/0089-rename-string-reflection-init.md</a><br>
&gt;<br>
&gt; Reviews are an important part of the Swift evolution process. All<br>
&gt; 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<br>
&gt; through constructive criticism and contribute to the direction of<br>
&gt; Swift. When writing your review, here are some questions you might<br>
&gt; 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<br>
&gt; 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>
<br>
</span>I&#39;m posting this on behalf of Dmitri Gribenko, and Max Moiseev, and<br>
myself.<br>
<br>
We would like to accept the proposal with one modification: rather than<br>
add an argument label, we&#39;d like to drop the String initializer<br>
altogether, making `&quot;\(expression)&quot;` the standard way to get a string<br>
representation of `expression`.<br>
<br>
Thanks,<br>
<span class="HOEnZb"><font color="#888888"><br>
--<br>
-Dave<br>
</font></span><div class="HOEnZb"><div class="h5"><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>