[swift-evolution] [Review] SE-0039 Modernizing Playground Literals

[Adrian Kashivskyy]

> What is your evaluation of the proposal?

+1. This is a good change.

> Is the problem being addressed significant enough to warrant a change to Swift?

Although playground literals are "hidden" when editing the playground in Xcode, the source code is still relevant. So yes, I think it is.

> Does this proposal fit well with the feel and direction of Swift?

Definetely. As playground literals are de facto compiler directives, the new syntax matches the naming convention of compiler directives. The `[# #]` syntax feels very out-of-place in Swift.

> If you have used other languages or libraries with a similar feature, how do you feel that this proposal compares to those?

No other language I used has such literals, so no.

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

I read the proposal.


Pozdrawiam – Regards,
Adrian Kashivskyy

> Wiadomość napisana przez Chris Lattner via swift-evolution <swift-evolution at swift.org> w dniu 08.03.2016, o godz. 00:54:
> 
> Hello Swift community,
> 
> The review of “ Modernizing Playground Literals” begins now and runs through March 9, 2016. The proposal is available here:
> 
> 	https://github.com/apple/swift-evolution/blob/master/proposals/0039-playgroundliterals.md <https://github.com/apple/swift-evolution/blob/master/proposals/0039-playgroundliterals.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:
> 
> 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,
> 
> -Chris
> 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/20160309/dac9ff72/attachment.html>