<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="">ES++ for exactly the same reasons. I use postfix increment because I didn’t even think of the completion angle until Mark brought it up. The fingers type what the fingers type.<div class=""><br class=""></div><div class="">I also support for the other many fine reasons previously mentioned in this thread: matches user expectations, the description is more commonly used in art than NUL, which remains obscure even if technically accurate. See also: <a href="https://en.wikipedia.org/wiki/Null-terminated_string" class="">https://en.wikipedia.org/wiki/Null-terminated_string</a>. I want to contribute to the “broad community support for renaming”.</div><div class=""><br class=""></div><div class="">That said, I’d prefer utf8String and utf8CString, but I suspect that’s a non-starter, and the initial pitch misidentifies the properties as methods.</div><div class=""><br class=""></div><div class="">— E</div><div class=""><br class=""></div><div class=""><br class=""><div class=""><div><blockquote type="cite" class=""><div class="">On Jul 24, 2016, at 11:39 AM, Mark Dalrymple 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 dir="ltr" class="">+1, mainly because if someone uses on-demand completion (like me) thinking it's called "nullTerminated", typing "null" will not complete if the method name is "nulTerminated"<div class=""><br class=""></div><div class="">++md</div><div class=""><br class=""></div></div></div></blockquote></div><br class=""></div></div></body></html>