<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=""><br class=""></div><div class="">To the Swift community,</div><div class=""><br class=""></div><div class="">May I put forth a couple of new names for the following protocol:</div><div class=""><br class=""></div><div class=""><br class=""></div><div class="">- CustomStringConvertible — rename as ‘Descriptive’ or as ‘Revealable’</div><div class=""><br class=""></div><div class=""><br class=""></div><div class="">Two goals for Swift is clarity and joy in use of the language, so I strongly feel that ‘Custom-‘ not be part of any new name here since it contributes little except verbosity, and ‘-String-‘ should be dropped too since ‘CustomStringConvertible’ has nothing to do with the String struct proper. The protocol only consists of the <b class="">var description</b>, after all.</div><div class=""><br class=""></div><div class="">Of course, the corollary would be ‘DebugDescriptive’ or ‘DebugRevealable’</div><div class=""><br class=""></div><div class="">I did consider ‘Describable’ as a name but to me ‘Descriptive’ looks and sounds better and captures the essence of what CustomStringConvertible really is. ‘Revealable’ as an alternate sounds, pardon the pun, almost as descriptive and has a bit of a classier ring to it.</div><div class=""><br class=""></div><div class="">This is a followup, albeit partial, to the final <span style="white-space: pre-wrap; background-color: rgb(255, 255, 255);" class="">review of proposal SE-0041 </span><span style="white-space: pre-wrap;" class="">which noted that the community was quite positive about the stated need to rename this and some other protocols, but just needs agreement on new names.</span></div><div class=""><br class=""></div><div class="">— Eric</div></body></html>