<div dir="ltr">+1; quick read.<div><br></div><div>Re #fileliteral vs. #resourceliteral, I think the latter makes sense because items are in the "Resources" folder of playgrounds. (The other day I tried referencing a file outside the playground and was confused when dragging it in made a copy.) You might also consider naming the parameter resourceFileName instead of resourceName so it's clear that the file extension is also required (which I assume it is(?)).</div><div><br></div><div>Is it necessary to include "literal" in the name? Isn't the fact that there's special compiler support enough to indicate that it's a literal-like value?</div><div class="gmail_extra"><br clear="all"><div><div class="gmail_signature"><div dir="ltr"><div>Jacob<br></div></div></div></div>
<br><div class="gmail_quote">On Mon, Mar 7, 2016 at 3:54 PM, Chris Lattner via swift-evolution <span dir="ltr"><<a href="mailto:swift-evolution@swift.org" target="_blank">swift-evolution@swift.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word"><div>Hello Swift community,</div><div><br>The review of “ Modernizing Playground Literals” begins now and runs through March 9, 2016. The proposal is available here:</div><div><br></div><div><span style="white-space:pre-wrap"> </span><a href="https://github.com/apple/swift-evolution/blob/master/proposals/0039-playgroundliterals.md" target="_blank">https://github.com/apple/swift-evolution/blob/master/proposals/0039-playgroundliterals.md</a></div><div></div><div><br></div><div>Reviews are an important part of the Swift evolution process. All reviews should be sent to the swift-evolution mailing list at:<br><span style="white-space:pre-wrap"> </span><a href="https://lists.swift.org/mailman/listinfo/swift-evolution" target="_blank">https://lists.swift.org/mailman/listinfo/swift-evolution</a><br><br>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:<br><br><b>What goes into a review?<br></b><br>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:<br><br><span style="white-space:pre-wrap"> </span>• What is your evaluation of the proposal?<br><span style="white-space:pre-wrap"> </span>• Is the problem being addressed significant enough to warrant a change to Swift?<br><span style="white-space:pre-wrap"> </span>• Does this proposal fit well with the feel and direction of Swift?<br><span style="white-space:pre-wrap"> </span>• If you have used other languages or libraries with a similar feature, how do you feel that this proposal compares to those?<br><span style="white-space:pre-wrap"> </span>• How much effort did you put into your review? A glance, a quick reading, or an in-depth study?<br><br>More information about the Swift evolution process is available at:<br><br><a href="https://github.com/apple/swift-evolution/blob/master/process.md" target="_blank">https://github.com/apple/swift-evolution/blob/master/process.md</a><br><br>Thank you,<br><br>-Chris</div><div>Review Manager</div></div><br>_______________________________________________<br>
swift-evolution mailing list<br>
<a href="mailto:swift-evolution@swift.org">swift-evolution@swift.org</a><br>
<a href="https://lists.swift.org/mailman/listinfo/swift-evolution" rel="noreferrer" target="_blank">https://lists.swift.org/mailman/listinfo/swift-evolution</a><br>
<br></blockquote></div><br></div></div>