<div style="white-space:pre-wrap">Ah. Now I see the use case. I'd counter, however, that these are weaknesses of the respective frameworks, and that literals as you propose them are rather like a thin version (in the motivating problem it's trying to solve) of the longed-for UXKit that'll supposedly unify all.<br><br>Even if we have these proposed literals, the various Apple-proprietary frameworks would have to be modified to accept them (to be expressible by them, in the new parlance). We could equally well appeal for the frameworks to be modified so that NS* types and UI* types play nicely together, without providing these pan-Swift facilities. Server code, for instance, could have little need for a font literal.<br></div><br><div class="gmail_quote"><div dir="ltr">On Mon, Jul 11, 2016 at 00:53 Erica Sadun via swift-evolution <<a href="mailto:swift-evolution@swift.org" target="_blank">swift-evolution@swift.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word">On Jul 10, 2016, at 11:43 PM, Zach Waldowski via swift-evolution <<a href="mailto:swift-evolution@swift.org" target="_blank">swift-evolution@swift.org</a>> wrote:<br></div><div style="word-wrap:break-word"><div><blockquote type="cite"><br><div>
<div><div style="font-family:Arial">I share the concern with others about the usefulness of these, but I also like your note about standardizing syntax, and really like that these merge together all the different syntaxes for literals we've seen.<br></div></div></div></blockquote><div><br></div></div></div><div style="word-wrap:break-word"><div>Literals enable you to write cross platform code with a minimum of </div><div>redundant and platform-configured code.</div><div><br></div><div>In today's Swift, you can say: let myColor = color literal and that code is </div><div>cross-compatible for all Apple platforms, whether UIColor, NSColor, and SKColor.</div><div>If you write that same request as let myColor = UIColor(...), it will no longer </div><div>compile on Cocoa.</div><div><br></div><div>I'm proposing to extend these existing behaviors to create common code inherently </div><div>universal tasks with common structure: NSFont/UIFont, point2/CGPoint/NSPoint, etc</div><div><br></div><div></div></div><div style="word-wrap:break-word"><div><blockquote type="cite"><div><div>
<div style="font-family:Arial">To that end, I'd like to modestly suggest that #literal.foo (as already written in the proposal) should be the canonical form of a literal in source text, whereas #foo is the one you see used in the code editor.</div></div></div></blockquote><div><br></div></div></div><div style="word-wrap:break-word"><div>I've already filed radars asking that the code editor let you see the raw unrendered literals</div><div>and heartily encourage duped radars to support that end.</div><div></div></div><div style="word-wrap:break-word"><div><br><blockquote type="cite"><div><div><div style="font-family:Arial"> I'm not a fan of namespacing in #literal, because every literal should obviously be a literal; I wouldn't ever recommend numerals fall under this proposal as written, for instance.</div></div></div></blockquote><div><br></div></div></div><div style="word-wrap:break-word"><div><div>The core team has suggested they'd like to use namespacing, especially with related</div><div>items that could otherwise spread and grow in an unmanaged way.</div></div><br></div>_______________________________________________<br>
swift-evolution mailing list<br>
<a href="mailto:swift-evolution@swift.org" target="_blank">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>
</blockquote></div>