[swift-evolution] [Review] SE-0027 Expose code unit initializers on String

[David Hart]

What is your evaluation of the proposal?
+1. I’ve never had to work with string byte representations but the proposal makes sense.

Is the problem being addressed significant enough to warrant a change to Swift?
It changes the standard library instead of the language, so I think it is warranted enough for that.

Does this proposal fit well with the feel and direction of Swift?
It does.

If you have used other languages or libraries with a similar feature, how do you feel that this proposal compares to those?
I have used the byte APIs on NSString in Objective-C. Sounds like it will bring Swift’s String up-par.

How much effort did you put into your review? A glance, a quick reading, or an in-depth study?
A quick reading.

> On 12 Feb 2016, at 01:41, Douglas Gregor via swift-evolution <swift-evolution at swift.org> wrote:
> 
> Hello Swift community,
> 
> The review of SE-0027 "Expose code unit initializers on String" begins now and runs through February 16, 2016. The proposal is available here:
> 
> https://github.com/apple/swift-evolution/blob/master/proposals/0027-string-from-code-units.md <https://github.com/apple/swift-evolution/blob/master/proposals/0027-string-from-code-units.md>
> Reviews are an important part of the Swift evolution process. All reviews should be sent to the swift-evolution mailing list at
> 
> https://lists.swift.org/mailman/listinfo/swift-evolution <https://lists.swift.org/mailman/listinfo/swift-evolution>
> or, if you would like to keep your feedback private, directly to the review manager. When replying, please try to keep the proposal link at the top of the message:
> 
> Proposal link:
> 
> https://github.com/apple/swift-evolution/blob/master/proposals/0027-string-from-code-units.md <https://github.com/apple/swift-evolution/blob/master/proposals/0027-string-from-code-units.md>
> Reply text
> 
> Other replies
>  <https://github.com/apple/swift-evolution#what-goes-into-a-review-1>What goes into a review?
> 
> The goal of the review process is to improve the proposal under review through constructive criticism and, eventually, determine 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
> 
> https://github.com/apple/swift-evolution/blob/master/process.md <https://github.com/apple/swift-evolution/blob/master/process.md>
> Thank you,
> 
> Doug Gregor
> 
> Review Manager
> 
> _______________________________________________
> 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/20160214/864c0602/attachment.html>