<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div class="">The literal in the name was:</div><div class=""><br class=""></div><div class="">1. To create an identifier that was long and unique enough to avoid the naming conflict previously experienced with #line for debug identifiers.</div><div class="">2. To clarify the role of the constructor, which is to create a literal playground reference, that can then be copied, dragged, etc within the playground editor.</div><div class="">3. To properly modify the constructor name rather than the argument name.</div><div class=""><br class=""></div><div class="">Other notes:</div><div class=""><br class=""></div><div class="">* There's a consistent use of lowercase identifiers rather than camelCase, which this proposal follows.</div><div class="">* While I personally prefer resourceliteral, fileliteral more closely followed the current art so got preferential mention.</div><div class="">* At some future date, I'd like to see the playground literal vocabulary expand (for example, URL) but that falls outside the scope of this proposal.</div><div class=""><br class=""></div><div class="">-- Erica</div><div class=""><br class=""></div><div class=""><br class=""></div><br class=""><div><blockquote type="cite" class=""><div class="">On Mar 7, 2016, at 5:15 PM, Jacob Bandes-Storch via swift-evolution <<a href="mailto:swift-evolution@swift.org" class="">swift-evolution@swift.org</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class="">+1; quick read.<div class=""><br class=""></div><div class="">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 class=""><br class=""></div><div class="">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" class=""><div class=""><div class="gmail_signature"><div dir="ltr" class=""><div class="">Jacob<br class=""></div></div></div></div>
<br class=""><div class="gmail_quote">On Mon, Mar 7, 2016 at 3:54 PM, Chris Lattner via swift-evolution <span dir="ltr" class=""><<a href="mailto:swift-evolution@swift.org" target="_blank" class="">swift-evolution@swift.org</a>></span> wrote:<br class=""><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word" class=""><div class="">Hello Swift community,</div><div class=""><br class="">The review of “ Modernizing Playground Literals” begins now and runs through March 9, 2016. The proposal is available here:</div><div class=""><br class=""></div><div class=""><span style="white-space:pre-wrap" class=""> </span><a href="https://github.com/apple/swift-evolution/blob/master/proposals/0039-playgroundliterals.md" target="_blank" class="">https://github.com/apple/swift-evolution/blob/master/proposals/0039-playgroundliterals.md</a></div><div class=""></div><div class=""><br class=""></div><div class="">Reviews are an important part of the Swift evolution process. All reviews should be sent to the swift-evolution mailing list at:<br class=""><span style="white-space:pre-wrap" class=""> </span><a href="https://lists.swift.org/mailman/listinfo/swift-evolution" target="_blank" class="">https://lists.swift.org/mailman/listinfo/swift-evolution</a><br class=""><br class="">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 class=""><br class=""><b class="">What goes into a review?<br class=""></b><br class="">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 class=""><br class=""><span style="white-space:pre-wrap" class=""> </span>• What is your evaluation of the proposal?<br class=""><span style="white-space:pre-wrap" class=""> </span>• Is the problem being addressed significant enough to warrant a change to Swift?<br class=""><span style="white-space:pre-wrap" class=""> </span>• Does this proposal fit well with the feel and direction of Swift?<br class=""><span style="white-space:pre-wrap" class=""> </span>• If you have used other languages or libraries with a similar feature, how do you feel that this proposal compares to those?<br class=""><span style="white-space:pre-wrap" class=""> </span>• How much effort did you put into your review? A glance, a quick reading, or an in-depth study?<br class=""><br class="">More information about the Swift evolution process is available at:<br class=""><br class=""><a href="https://github.com/apple/swift-evolution/blob/master/process.md" target="_blank" class="">https://github.com/apple/swift-evolution/blob/master/process.md</a><br class=""><br class="">Thank you,<br class=""><br class="">-Chris</div><div class="">Review Manager</div></div><br class="">_______________________________________________<br class="">
swift-evolution mailing list<br class="">
<a href="mailto:swift-evolution@swift.org" class="">swift-evolution@swift.org</a><br class="">
<a href="https://lists.swift.org/mailman/listinfo/swift-evolution" rel="noreferrer" target="_blank" class="">https://lists.swift.org/mailman/listinfo/swift-evolution</a><br class="">
<br class=""></blockquote></div><br class=""></div></div>
_______________________________________________<br class="">swift-evolution mailing list<br class=""><a href="mailto:swift-evolution@swift.org" class="">swift-evolution@swift.org</a><br class="">https://lists.swift.org/mailman/listinfo/swift-evolution<br class=""></div></blockquote></div><br class=""></body></html>