[swift-evolution] [swift-evolution-announce] [Review] SE-0128: Change failable UnicodeScalar initializers to failable
cantrell at pobox.com
Fri Jul 22 11:09:00 CDT 2016
Strongly in favor.
I agree that the existing behavior could even arguably be filed as a bug, since there is no static isValidCodePoint() method an API client can call first.
Aside: I would still like to see String follow a similar convention of failing on initialization for UTF-16 strings containing bad surrogate pairs.
> On Jul 21, 2016, at 5:28 PM, Chris Lattner <clattner at apple.com> wrote:
> Hello Swift community,
> The review of "SE-0128: Change failable UnicodeScalar initializers to failable" begins now and runs through July 24. The proposal is available here:
> Reviews are an important part of the Swift evolution process. All reviews should be sent to the swift-evolution mailing list at
> or, if you would like to keep your feedback private, directly to the review manager.
> What goes into a review?
> The goal of the review process is to improve the proposal under review through constructive criticism and contribute to the direction of Swift. When writing your review, here are some questions you might want to answer in your review:
> * What is your evaluation of the proposal?
> * Is the problem being addressed significant enough to warrant a change to Swift?
> * Does this proposal fit well with the feel and direction of Swift?
> * If you have used other languages or libraries with a similar feature, how do you feel that this proposal compares to those?
> * How much effort did you put into your review? A glance, a quick reading, or an in-depth study?
> More information about the Swift evolution process is available at
> Thank you,
> -Chris Lattner
> Review Manager
> swift-evolution-announce mailing list
> swift-evolution-announce at swift.org
More information about the swift-evolution