<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div class="">The great advantage of basic renaming is that migration is super-simple. And now that I think about it, <font face="Courier" class="">CustomStringRepresentable</font> is probably a lot better than <span style="font-family: Courier;" class="">CustomStringRepresentationExpressible</span></div><div class=""><br class=""></div><div class="">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 class=""><br class=""></div><div class="">-- E</div><div class="">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 class=""><br class=""></div><div class=""><br class=""></div><div><blockquote type="cite" class=""><div class="">On Dec 15, 2015, at 10:47 AM, Matthew Johnson <<a href="mailto:matthew@anandabits.com" class="">matthew@anandabits.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><meta http-equiv="Content-Type" content="text/html charset=utf-8" class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div class="">Thanks for your input Erica! I would be happy with any convention that establishes clarity and consistency.</div><div class=""><br class=""></div><div class="">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 class=""><br class=""></div><div class="">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 class=""><br class=""></div><div class="">Matthew</div><br class=""><div class=""><div class=""><blockquote type="cite" class=""><div class="">On Dec 15, 2015, at 11:39 AM, Erica Sadun via swift-evolution <<a href="mailto:swift-evolution@swift.org" class="">swift-evolution@swift.org</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><meta http-equiv="Content-Type" content="text/html charset=utf-8" class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div class="">And adding:</div><div class=""><br class=""></div><div class="">I *hate* <font face="Courier" class="">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 class=""><br class=""></div><div class="">* can be initialized from: <font face="Courier" class="">Instantiable, Initializable</font></div><div class="">* can be converted to: <font face="Courier" class="">Expressible, Presentable, Projectable</font></div><div class="">* can be represented as and instantiated by: <font face="Courier" class="">Convertible</font></div><div class=""><br class=""></div><div class="">For example, <font face="Courier" class="">IntegerLiteralInitializable</font>, <font face="Courier" class="">CustomStringRepresentationExpressible</font>, and <font face="Courier" class="">DoubleTypeConvertible</font>.</div><div class=""><br class=""></div><div class="">-- Erica</div></div><div class=""><br class=""></div><br class=""><div class=""><blockquote type="cite" class=""><div class="">On Dec 15, 2015, at 9:28 AM, Matthew Johnson via swift-evolution <<a href="mailto:swift-evolution@swift.org" class="">swift-evolution@swift.org</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><meta http-equiv="Content-Type" content="text/html charset=utf-8" class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div class="">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 class=""><br class=""></div><div class="">You can find the draft here: <a href="https://github.com/anandabits/swift-evolution/blob/conversion-protocol-conventions/proposals/0000-conversion-protocol-conventions.md" class="">https://github.com/anandabits/swift-evolution/blob/conversion-protocol-conventions/proposals/0000-conversion-protocol-conventions.md</a></div><div class=""><br class=""></div><div class="">The little feedback I did receive was positive.</div><div class=""><br class=""></div><div class="">Matthew</div><br class=""><div class=""><blockquote type="cite" class=""><div class="">On Dec 12, 2015, at 8:40 PM, Matthew Johnson via swift-evolution <<a href="mailto:swift-evolution@swift.org" class="">swift-evolution@swift.org</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><meta http-equiv="Content-Type" content="text/html charset=us-ascii" class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">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 class=""><br class=""></div><div class="">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" class="">https://github.com/anandabits/swift-evolution/blob/conversion-protocol-conventions/proposals/0000-conversion-protocol-conventions.md</a>.</div><div class=""><br class=""></div><div class="">Thanks,</div><div class="">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="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;" class="">
</div>
_______________________________________________<br class="">swift-evolution mailing list<br class=""><a href="mailto:swift-evolution@swift.org" class="">swift-evolution@swift.org</a><br class=""><a href="https://lists.swift.org/mailman/listinfo/swift-evolution" class="">https://lists.swift.org/mailman/listinfo/swift-evolution</a><br class=""></div></blockquote></div><br class="">
<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="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;" class="">
</div>
_______________________________________________<br class="">swift-evolution mailing list<br class=""><a href="mailto:swift-evolution@swift.org" class="">swift-evolution@swift.org</a><br class=""><a href="https://lists.swift.org/mailman/listinfo/swift-evolution" class="">https://lists.swift.org/mailman/listinfo/swift-evolution</a><br class=""></div></blockquote></div><br class="">
<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="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;" class="">
</div>
_______________________________________________<br class="">swift-evolution mailing list<br class=""><a href="mailto:swift-evolution@swift.org" class="">swift-evolution@swift.org</a><br class=""><a href="https://lists.swift.org/mailman/listinfo/swift-evolution" class="">https://lists.swift.org/mailman/listinfo/swift-evolution</a><br class=""></div></blockquote></div><br class=""></div></div></div></blockquote></div><br class=""></body></html>