<div style="white-space:pre-wrap">> p.s. Does anyone ever actually use debugString stuff? I love it in concept but I find that I use it about 0% of the time<br>Composite types (array, optional, ...) display debugString output </div><br><div class="gmail_quote"><div dir="ltr">On Tue, Dec 15, 2015 at 20:59 Erica Sadun 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"><div style="word-wrap:break-word"><div>The great advantage of basic renaming is that migration is super-simple. And now that I think about it, <font face="Courier">CustomStringRepresentable</font> is probably a lot better than <span style="font-family:Courier">CustomStringRepresentationExpressible</span></div><div><br></div><div>It's easy enough to take some time, throw some options out there, and come up with names that better represent the concepts in question (the big win of your proposal) and then vote for the best.</div></div><div style="word-wrap:break-word"><div><br></div><div>-- E</div></div><div style="word-wrap:break-word"><div>p.s. Does anyone ever actually use debugString stuff? I love it in concept but I find that I use it about 0% of the time</div></div><div style="word-wrap:break-word"><div><br></div><div><br></div><div><blockquote type="cite"><div>On Dec 15, 2015, at 10:47 AM, Matthew Johnson <<a href="mailto:matthew@anandabits.com" target="_blank">matthew@anandabits.com</a>> wrote:</div><br><div><div style="word-wrap:break-word"><div>Thanks for your input Erica! I would be happy with any convention that establishes clarity and consistency.</div><div><br></div><div>I wrote the proposal the way I did as it is the minimum change from current state that would establish clarity and consistency. My rationale was the smaller the change, the greater the chance of acceptance.</div><div><br></div><div>It would be great to hear whether the community would prefer minimal change or wants to make a larger change if a better end result is possible that way.</div><div><br></div><div>Matthew</div><br><div><div><blockquote type="cite"><div>On Dec 15, 2015, at 11:39 AM, Erica Sadun via swift-evolution <<a href="mailto:swift-evolution@swift.org" target="_blank">swift-evolution@swift.org</a>> wrote:</div><br><div><div style="word-wrap:break-word"><div>And adding:</div><div><br></div><div>I *hate* <font face="Courier">Convertible</font> in its current form. Per your current write-up, the protocols should cover initialized from, converted to, and a mix. Let me suggest:<div><br></div><div>* can be initialized from: <font face="Courier">Instantiable, Initializable</font></div><div>* can be converted to: <font face="Courier">Expressible, Presentable, Projectable</font></div><div>* can be represented as and instantiated by: <font face="Courier">Convertible</font></div><div><br></div><div>For example, <font face="Courier">IntegerLiteralInitializable</font>, <font face="Courier">CustomStringRepresentationExpressible</font>, and <font face="Courier">DoubleTypeConvertible</font>.</div><div><br></div><div>-- Erica</div></div><div><br></div><br><div><blockquote type="cite"><div>On Dec 15, 2015, at 9:28 AM, Matthew Johnson via swift-evolution <<a href="mailto:swift-evolution@swift.org" target="_blank">swift-evolution@swift.org</a>> wrote:</div><br><div><div style="word-wrap:break-word"><div>Bumping this thread. There wasn’t much response to the initial post, which may have been because Saturday night is probably not the best time to post a proposal. :)</div><div><br></div><div>You can find the draft here: <a href="https://github.com/anandabits/swift-evolution/blob/conversion-protocol-conventions/proposals/0000-conversion-protocol-conventions.md" target="_blank">https://github.com/anandabits/swift-evolution/blob/conversion-protocol-conventions/proposals/0000-conversion-protocol-conventions.md</a></div><div><br></div><div>The little feedback I did receive was positive.</div><div><br></div><div>Matthew</div><br><div><blockquote type="cite"><div>On Dec 12, 2015, at 8:40 PM, Matthew Johnson via swift-evolution <<a href="mailto:swift-evolution@swift.org" target="_blank">swift-evolution@swift.org</a>> wrote:</div><br><div><div style="word-wrap:break-word">I have drafted a proposal to establish precise conventional meaning for the use of `Convertible`, `Representable`, and `Projectable` protocol suffixes. The proposal would require renaming `CustomStringConvertible` and `CustomDebugStringConvertible` to `CustomStringProjectable` and `CustomDebugStringProjectable` respectively<div><br></div><div>I am seeking input on the proposal before submitting a PR. The full draft can found at <a href="https://github.com/anandabits/swift-evolution/blob/conversion-protocol-conventions/proposals/0000-conversion-protocol-conventions.md" target="_blank">https://github.com/anandabits/swift-evolution/blob/conversion-protocol-conventions/proposals/0000-conversion-protocol-conventions.md</a>.</div><div><br></div><div>Thanks,</div><div>Matthew</div>
<img src="https://u2002410.ct.sendgrid.net/wf/open?upn=eLFMrKDT8iBxZ-2Fbnk-2BZqvSchNN-2FvYXdceA0T7VxwkAdaxTdH0mXQ7mRo-2F2qQFnRuVPaZwbORYWW5j3el68FVldanVpU9kM6-2BbQK4r3MIU3QDH9resexvEbB-2FM7mutvWudU7QCwFUxMIhyf4xH9bGKn4sm2Q4XX2wyvAa-2BSeIFIlX-2BO4b-2F4jLCvVB-2FKYy5lVCwu0YX1dBKh1H-2F1Zkpll1ukj4S8SO5DnNJgLX5jU2CvU-3D" alt="" width="1" height="1" border="0" style="min-height:1px!important;width:1px!important;border-width:0!important;margin-top:0!important;margin-bottom:0!important;margin-right:0!important;margin-left:0!important;padding-top:0!important;padding-bottom:0!important;padding-right:0!important;padding-left:0!important">
</div>
_______________________________________________<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" target="_blank">https://lists.swift.org/mailman/listinfo/swift-evolution</a><br></div></blockquote></div><br>
<img src="https://u2002410.ct.sendgrid.net/wf/open?upn=r5jpKsi6nat7oa43lpCLi5GRGm2utDkbDscuFklXZ2cB76cRuER-2FAwgvcCyku-2FjRDCsiQVYDWmaqj5DwQpUlsrMez-2BJjj-2BQhimLEuLlOLuD2TwHibY4hkAoVYcQFhm-2BxYiV3vKcWR4SNGjcDH-2FnYDAZdG2wLNn6OAX8EeHg6PxqQXnIjnSytH7WGkS-2BjD4xtfSV-2BOv34GMgYnorCUu-2FyZcAaYS-2B-2FDkOz8-2Fivkq92OMg-3D" alt="" width="1" height="1" border="0" style="min-height:1px!important;width:1px!important;border-width:0!important;margin-top:0!important;margin-bottom:0!important;margin-right:0!important;margin-left:0!important;padding-top:0!important;padding-bottom:0!important;padding-right:0!important;padding-left:0!important">
</div>
_______________________________________________<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" target="_blank">https://lists.swift.org/mailman/listinfo/swift-evolution</a><br></div></blockquote></div><br>
<img src="https://u2002410.ct.sendgrid.net/wf/open?upn=eLFMrKDT8iBxZ-2Fbnk-2BZqvSchNN-2FvYXdceA0T7VxwkAfVENjA7gVgeqjUyI9-2FcWnYaIkXk4uqCarhV8rV7P99McLAPbMD4gDh7-2Bgo9Cm138tI8dkfjn8cL0tHBsBeOQ7EC3V4H6AvS5lN8yGxtcPhi7WS9979ddmVkk9560qcYS9SiZeNO-2B17zasP1RjUu0wey0bhRuINDa0no31eLR2F-2FVwgua-2Bb7tsw-2BgwjQnWbiAw-3D" alt="" width="1" height="1" border="0" style="min-height:1px!important;width:1px!important;border-width:0!important;margin-top:0!important;margin-bottom:0!important;margin-right:0!important;margin-left:0!important;padding-top:0!important;padding-bottom:0!important;padding-right:0!important;padding-left:0!important">
</div>
_______________________________________________<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" target="_blank">https://lists.swift.org/mailman/listinfo/swift-evolution</a><br></div></blockquote></div><br></div></div></div></blockquote></div><br>
<img src="https://u2002410.ct.sendgrid.net/wf/open?upn=1p9Jer2O6jVE9KWvo-2B9iUaEyN8slp4IizyiLwsfp54PJJLVSqORLbgx3KlihI6f9m7S7dmGdob1VkGQI-2FCucsK1zePHYjwoNSotWu0jsVEMkDx75B3q-2B0ok1ZDACaWFJYFLc7HMxgeS-2FhCabDZIFC2-2B56MZEnBIQ9bO-2FSkJ0y10Byxpvh-2BOmoZO7Os0M0dM-2B1KYxqCl6JzjnWRFtkGDGYL4PQWb452IZgD3-2F0wAQCWA-3D" alt="" width="1" height="1" border="0" style="min-height:1px!important;width:1px!important;border-width:0!important;margin-top:0!important;margin-bottom:0!important;margin-right:0!important;margin-left:0!important;padding-top:0!important;padding-bottom:0!important;padding-right:0!important;padding-left:0!important">
</div>
_______________________________________________<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>