<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><blockquote type="cite" class=""><div class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div 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 class="Apple-tab-span" style="white-space:pre"> </span><a href="https://github.com/apple/swift-evolution/blob/master/proposals/0039-playgroundliterals.md" class="">https://github.com/apple/swift-evolution/blob/master/proposals/0039-playgroundliterals.md</a></div><div class=""></div><div class=""></div></div></div></blockquote><br class=""><blockquote type="cite" class=""><div class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div class=""><span class="Apple-tab-span" style="white-space: pre;"> </span>• What is your evaluation of the proposal?</div></div></div></blockquote><div><br class=""></div>+1. I have a slight preference for “fileliteral” over “resourceliteral”. I don’t see a great advantage of one over the other, so I’d use the name that is closer to the existing terminology just so it’s more apparent that the functionality hasn’t changed, only the syntax.</div><div><br class=""></div><div>—CK</div><div><br class=""></div></body></html>