[swift-evolution] [Draft] Fix a typo in two String methods
nevin.brackettrozinsky at gmail.com
Sun Jul 24 17:53:00 CDT 2016
I think the hypothetical alternative would be `nullTerminatedCString` for
one and `nullTerminatedUTF8` for the other.
On Sun, Jul 24, 2016 at 6:34 PM, Erica Sadun via swift-evolution <
swift-evolution at swift.org> wrote:
> > On Jul 24, 2016, at 3:45 PM, Dave Abrahams via swift-evolution <
> swift-evolution at swift.org> wrote:
> > Xiaodi Wu via swift-evolution <swift-evolution at ...> writes:
> >> In `String`, the methods `nulTerminatedUTF8` and
> >> nulTerminatedUTF8CString` have the word "null" misspelled
> > Whoa. Isn't "Cstring" redundant with "null-terminated?"
> One would hope so. A series of characters terminated by a zero byte.
> /// A contiguously stored null-terminated UTF-8 representation of
> /// the string.
> /// This is a variation on nulTerminatedUTF8 that creates an array
> /// of element type CChar for use with CString API's.
> I think utf8String and utf8CString capture both meanings. I know they're
> a little redundant but they get the meaning across, use CString term of
> art, and are pithy compared to any alternatives (like "representation",
> -- E
> swift-evolution mailing list
> swift-evolution at swift.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the swift-evolution