[swift-evolution] Mark UnicodeScalar.utf16 and UnicodeScalar.UTF16View as public

Robert Widmann devteam.codafi at gmail.com
Fri Sep 23 11:02:05 CDT 2016

+1.  This is a bug fix in my mind, evolution is merely a formality.

Ship it

~Robert Widmann

2016/09/22 18:59、Eli Perkins via swift-evolution <swift-evolution at swift.org> のメッセージ:

> Hey all!
> I picked up SR-2627 (https://bugs.swift.org/browse/SR-2627) from the Swift JIRA project. The ticket states:
> > UnicodeScalar.utf16 does not have access modifier and therefore is internal but should be public, as well as UnicodeScalar.UTF16View.
> The ticket is written in a way that makes it seem as though this change would match the behavior of APIs such as the UTF accessors on `String`.
> Additionally, `UnicodeScalar.utf16` and `Unicodescalar.UTF16View` seem to be created in `UnicodeScalar.swift`, but not used elsewhere, indicating that these properties were intended to be exposed to developers as part of the stdlib.
> After submitting a pull request to implement this (https://github.com/apple/swift/pull/4929, Maxim Moiseev and Michael Gottesman mentioned that since this does modify the public API, a proposal should go through swift-evolution to address this.
> I wanted to kick off the discussion here and get feedback from the mailing list.
> Looking forward to chatting about this!
> Eli Perkins
> _______________________________________________
> 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/20160923/b6c31764/attachment.html>

More information about the swift-evolution mailing list