[swift-evolution] [swift-evolution-announce] [Review] SE-0168: Multi-Line String Literals

[T.J. Usiyan]

+1 with the clarifications provided in the thread.

On Sun, Apr 9, 2017 at 4:44 AM, Howard Lovatt via swift-evolution <
swift-evolution at swift.org> wrote:

> Review of SE-0168 "Multi-Line String Literals"
>
> • What is your evaluation of the proposal?
>
> Yes good idea. Though I am not clear as to whether the final return before
> the closing """ is included in the literal or not. If not, would a blank
> line before """ enclose a return at the end. If yes, would the closing """
> have to be on the same line to prevent a return at the end. It doesn't
> really matter which option, but it wasn't clear to me what happens.
>
> • Is the problem being addressed significant enough to warrant a change to
> Swift?
>
> Yes. Very handy on server side code.
>
> • Does this proposal fit well with the feel and direction of Swift?
>
> Yes, with the push onto server side it is a nice addition.
>
> • If you have used other languages or libraries with a similar feature,
> how do you feel that this proposal compares to those?
>
> Yes. Lots of languages have similar.
>
> • How much effort did you put into your review? A glance, a quick reading,
> or an in-depth study?
>
> Quick read.
>
>
> -- Howard.
>
> On 7 Apr 2017, at 5:35 am, Joe Groff <jgroff at apple.com> wrote:
>
> review of SE-0168 "Multi-Line String Literals" begins now and runs through
> April 12, 2017. The proposal is available here:
>
> https://github.com/apple/swift-evolution/blob/master/
> proposals/0168-multi-line-string-literals.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
>
> 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/0167-swift-encoders.md
>
>
> Reply text
>
> Other replies
>
>
> *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?
>
>
> _______________________________________________
> 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/20170409/ed8e99cf/attachment.html>