<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><br class=""><div><blockquote type="cite" class=""><div class="">On Dec 15, 2015, at 11:15 AM, Matthew Johnson <<a href="mailto:matthew@anandabits.com" class="">matthew@anandabits.com</a>> wrote:</div><div class=""><div dir="auto" class=""><blockquote type="cite" class=""><div class=""><div class="">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></blockquote><div class=""><br class=""></div><div class="">Representable is what I would have used if I wasn't trying to make a minimal change or if RawRepresentable didn't already use it for bidirectional conversion, so I agree that it is better than both Expressible and Projectable.</div><div class=""><br class=""></div><div class="">Matthew</div><div class=""><br class=""></div><div class=""><br class=""></div></div></div></blockquote></div><br class=""><div class="">Let's run with the idea that everything is up for grabs and that better names will better serve the developer community in the long run. In such a case, if the core naming patterns were established as Convertible for bidirectional conversion, would RawConvertible be such a bad thing?</div><div class=""><br class=""></div><div class="">-- Erica</div><div class=""><br class=""></div></body></html>