[swift-evolution-announce] [Rejected] SE-0010 "Add StaticString.UnicodeScalarView"

Douglas Gregor dgregor at apple.com
Tue Feb 23 00:15:56 CST 2016


(My apologies for the very late response; the core team discussed this proposal in mid-January)

The public review of SE-0010 “Add StaticString.UnicodeScalarView” ran from January 6...8, 2016. The proposal has been rejected.

	https://github.com/apple/swift-evolution/blob/master/proposals/0010-add-staticstring-unicodescalarview.md

While the addition of StaticString.UnicodeScalarView is a useful feature by itself, the core team felt that it would be inconsistent just to add this narrow set of APIs for Unicode scalars. StaticString itself is a bit odd: it’s UTF-8 API works differently from String, there is no provision for UTF-16/32, etc. If StaticString is to gain Unicode support, it should be done comprehensively, not piecemeal. Moreover, with the aforementioned String re-evaluation underway, it is possible that StaticString itself might change considerably or even be obsoleted.

	Doug Gregor
	Review Manager

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.swift.org/pipermail/swift-evolution-announce/attachments/20160222/25f6304d/attachment.html>


More information about the swift-evolution-announce mailing list