<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div></div><div>Maybe... It's just a property, though. I <i>think</i> if something's moving into the Syntax thing, I'd rather look for a way to move string interpolation there. Maybe.</div><div><br></div><div>- Dave Sweeris</div><div><br>On Jul 1, 2016, at 14:24, Xiaodi Wu via swift-evolution <<a href="mailto:swift-evolution@swift.org">swift-evolution@swift.org</a>> wrote:<br><br></div><blockquote type="cite"><div>Perhaps another candidate for sinking into `Syntax`?<br><div class="gmail_quote"><div dir="ltr">On Fri, Jul 1, 2016 at 14:23 Dmitri Gribenko via swift-evolution <<a href="mailto:swift-evolution@swift.org">swift-evolution@swift.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On Fri, Jul 1, 2016 at 12:16 PM, Eric Habberstad via swift-evolution<br>
<<a href="mailto:swift-evolution@swift.org" target="_blank">swift-evolution@swift.org</a>> wrote:<br>
><br>
> To the Swift community,<br>
><br>
> May I put forth a couple of new names for the following protocol:<br>
><br>
><br>
> - CustomStringConvertible — rename as ‘Descriptive’ or as ‘Revealable’<br>
><br>
><br>
> Two goals for Swift is clarity and joy in use of the language, so I strongly<br>
> feel that ‘Custom-‘ not be part of any new name here since it contributes<br>
> little except verbosity<br>
<br>
Hi Eric,<br>
<br>
This protocol was called Printable before, but it caused a lot of<br>
confusion for developers, and was guiding the developers toward<br>
writing incorrect APIs. We have seen a lot of developers writing code<br>
like this:<br>
<br>
func printAll(_ values: [Printable]) {<br>
for v in values { print(v) }<br>
}<br>
<br>
This code is unnecessarily restrictive since in Swift everything can<br>
be converted into a String.<br>
<br>
func printAll(_ values: [Any]) {<br>
for v in values { print(v) }<br>
}<br>
<br>
The same goes for retrieving debug descriptions and mirrors. Any<br>
value can do that. It is just that some values can opt into<br>
customizing this behavior.<br>
<br>
Thus, we renamed the protocols, adding the Custom~ prefix. Our<br>
intention was to encourage only conformances to these protocols, and<br>
discourage writing APIs against them.<br>
<br>
Dmitri<br>
<br>
--<br>
main(i,j){for(i=2;;i++){for(j=2;j<i;j++){if(!(i%j)){j=0;break;}}if<br>
(j){printf("%d\n",i);}}} /*Dmitri Gribenko <<a href="mailto:gribozavr@gmail.com" target="_blank">gribozavr@gmail.com</a>>*/<br>
_______________________________________________<br>
swift-evolution mailing list<br>
<a href="mailto:swift-evolution@swift.org" target="_blank">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>
</blockquote></div>
</div></blockquote><blockquote type="cite"><div><span>_______________________________________________</span><br><span>swift-evolution mailing list</span><br><span><a href="mailto:swift-evolution@swift.org">swift-evolution@swift.org</a></span><br><span><a href="https://lists.swift.org/mailman/listinfo/swift-evolution">https://lists.swift.org/mailman/listinfo/swift-evolution</a></span><br></div></blockquote></body></html>