<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=""><br class=""><div><blockquote type="cite" class=""><div class="">On Dec 21, 2015, at 15:55 , Tino Heth 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=""><div class=""><br class=""><blockquote type="cite" class="">I suggest reinstating the C convention of using single-quotes for delimiting Characters.<br class=""></blockquote>I rarely use chars, but from a theoretical standpoint, I'm not so happy with the ambiguity as well…<br class="">But one suggestion if you want to make a proposal:<br class="">Char has a fixed length (well, at least that was the case before unicode ;-), so there is no need for a closing delimiter. Leaving the second ' (or whatever might be used) out would save one out of three keystrokes and no one could try to create characters like<br class="">'this isn't allowed here'<br class=""></div></div></blockquote></div><br class=""><div class="">Unicode is incredibly important, as is deciding whether you want to create a Character or UnicodeScalar (or some other type). In practice I don't think either Character or UnicodeScalar is common enough to <i class="">deserve</i> a special syntax.</div><div class=""><br class=""></div><div class="">Andrew, you said your use case is a compiler? I believe Dmitri and Dave have some ideas for how better to work with text-like structural data (code, markup, JSON, etc), but they're not ready to share yet. Superficially making Character more convenient won't really help with the rest of the issues in this space; a larger model is needed.</div><div class=""><br class=""></div><div class="">Jordan</div></body></html>