[swift-evolution] [Draft] Fix a typo in two String methods

Xiaodi Wu xiaodi.wu at gmail.com
Sun Jul 24 14:59:23 CDT 2016

Oops. Written in a hurry. I will fix all inaccuracies identified so far.
On Sun, Jul 24, 2016 at 14:50 Erica Sadun via swift-evolution <
swift-evolution at swift.org> wrote:

> 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.
> 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: https://en.wikipedia.org/wiki/Null-terminated_string. I want to
> contribute to the “broad community support for renaming”.
> 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.
> — E
> On Jul 24, 2016, at 11:39 AM, Mark Dalrymple via swift-evolution <
> swift-evolution at swift.org> wrote:
> +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"
> ++md
> _______________________________________________
> swift-evolution mailing list
> swift-evolution at swift.org
> https://lists.swift.org/mailman/listinfo/swift-evolution
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.swift.org/pipermail/swift-evolution/attachments/20160724/4b356862/attachment.html>

More information about the swift-evolution mailing list