<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div><br></div><blockquote type="cite"><div><meta http-equiv="Content-Type" content="text/html charset=utf-8"><div class="">The great advantage of basic renaming is that migration is super-simple. </div></div></blockquote><div><br></div><div><span style="background-color: rgba(255, 255, 255, 0);">Renaming is simple but communicating and re-educating everyone using Swift is somewhat less so. I don't mind it but imagine some would and some will argue against a larger change on that basis. Personally, I would like it if we go with the best names we can come up with so I do nudge in this direction.</span></div><div><br></div><br><blockquote type="cite"><div><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><br></div><div>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><br></div><div>Matthew</div><div><br></div><div><br></div></body></html>