<div dir="ltr">Sorry for the second email, but there's one link in particular that I think might be valuable (and is not easily found any other way). This little discussion by Chris Lattner discusses the dynamic nature of some popular programming languages compared to Swift, and has some explanation as to why Swift does things its way. <a href="https://lists.swift.org/pipermail/swift-evolution/Week-of-Mon-20151207/001948.html">https://lists.swift.org/pipermail/swift-evolution/Week-of-Mon-20151207/001948.html</a><div><div><div><br></div><div>Best,</div><div>Austin</div></div></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Oct 31, 2017 at 1:39 PM, Austin Zheng <span dir="ltr"><<a href="mailto:austinzheng@gmail.com" target="_blank">austinzheng@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">To expand on this, most (if not all) the proposals in the list of proposals on GitHub (<a href="https://github.com/apple/swift-evolution/tree/master/proposals" target="_blank">https://github.com/apple/<wbr>swift-evolution/tree/master/<wbr>proposals</a>) have a "Rationale" link to a mailing list archive post by one of the Swift core team members explaining why a certain decision was reached. Those are probably worth looking through. Some of the simpler and less controversial proposals have almost no explanation, but the larger and controversial proposals have extensively written-up rationale posts.<div><br></div><div>Best,</div><div>Austin</div></div><div class="HOEnZb"><div class="h5"><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Oct 31, 2017 at 12:25 PM, David Sweeris via swift-users <span dir="ltr"><<a href="mailto:swift-users@swift.org" target="_blank">swift-users@swift.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Specifically WRT to double quotes for characters, the Commonly Rejected Changes doc (<a href="https://github.com/apple/swift-evolution/blob/master/commonly_proposed.md" rel="noreferrer" target="_blank">https://github.com/apple/swif<wbr>t-evolution/blob/master/common<wbr>ly_proposed.md</a>) says, "Swift takes the approach of highly valuing Unicode. However, there are multiple concepts of a character that could make sense in Unicode, and none is so much more commonly used than the others that it makes sense to privilege them. We'd rather save single quoted literals for a greater purpose (e.g. non-escaped string literals)."<br>
<br>
Otherwise, off the top of my head I'm not sure. If it's a particularly controversial decision, there's a fair chance it's come up on the swift-evolution list, though, so maybe search its archives?<br>
<br>
Hope that helps,<br>
- Dave Sweeris<br>
<div class="m_5500505783109430148HOEnZb"><div class="m_5500505783109430148h5"><br>
> On Oct 31, 2017, at 8:52 AM, Michael Rogers via swift-users <<a href="mailto:swift-users@swift.org" target="_blank">swift-users@swift.org</a>> wrote:<br>
><br>
> Hi, All:<br>
><br>
> I’m giving a presentation on Swift this weekend, and am trying to find justification for some of the design decisions that they made. Is there anything out there that goes into the detail of this? Like … why did the use “ for characters, or \() for String interpolation?<br>
><br>
> Thanks,<br>
><br>
> Michael<br>
> ______________________________<wbr>_________________<br>
> swift-users mailing list<br>
> <a href="mailto:swift-users@swift.org" target="_blank">swift-users@swift.org</a><br>
> <a href="https://lists.swift.org/mailman/listinfo/swift-users" rel="noreferrer" target="_blank">https://lists.swift.org/mailma<wbr>n/listinfo/swift-users</a><br>
<br>
______________________________<wbr>_________________<br>
swift-users mailing list<br>
<a href="mailto:swift-users@swift.org" target="_blank">swift-users@swift.org</a><br>
<a href="https://lists.swift.org/mailman/listinfo/swift-users" rel="noreferrer" target="_blank">https://lists.swift.org/mailma<wbr>n/listinfo/swift-users</a><br>
</div></div></blockquote></div><br></div>
</div></div></blockquote></div><br></div>