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:
• Is the problem being addressed significant enough to warrant a change to Swift?
Its not a change but an extension to the language that feels entirely natural.
• Does this proposal fit well with the feel and direction of Swift?
Yes, see above,
• If you have used other languages or libraries with a similar feature, how do you feel that this proposal compares to those?
Not really, as the String type in swift is fairly complex. However I have done a fair bit of string parsing, and this change will make string parsing easier and more like ascii-string parsing.
• How much effort did you put into your review? A glance, a quick reading, or an in-depth study?
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:
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:
More information about the Swift evolution process is available at:
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:
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:
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:
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?
Obvious +1. I don't have much else to say; this is a solid and useful
addition.
- 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?
Yes. Swift already has some of the best Unicode handling among languages
today, so fleshing out that support is welcome.
···
On Fri, May 12, 2017 at 1:51 PM Ted Kremenek via swift-evolution < swift-evolution@swift.org> wrote:
- 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?
Quick read.
More information about the Swift evolution process is available at:
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:
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:
It would be nice if character was made to be like a string of exactly
length 1 (cannot be empty) and implemented the new string protocol like the
new string slice does. This way string, string slice, and character could
be used interchangeably when programming to the protocol.
-- Howard.
···
On 13 May 2017 at 11:52, Nicholas Maccharoli <nmaccharoli@gmail.com> wrote:
+1
- Nick
2017年5月13日(土) 10:06 Howard Lovatt via swift-evolution <
swift-evolution@swift.org>:
+1
-- Howard.
On 13 May 2017, at 6:41 am, Ted Kremenek <kremenek@apple.com> wrote:
Hello Swift community,
The review of *SE-0178: Add unicodeScalars property to Character* begins
now and runs through *May 17, 2017*.
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:
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: