<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div></div><div>But the question is, why does this need to affect the code base?</div><div><br></div><div>In the article you attached, they mention the antiquated one-line calculator display. The issue with that display is not the data stored in the calculator; it’s the display itself. An upgrade to (say) a Texas Instruments Inspire or whatever the newest TI calculator is (in my day we used an 83 or 84) only changes the display of the data; after all, you input that data will old fashioned buttons as well. The calculator isn’t doing any magic with the data itself in order to display that. If you want nicely formatted fractions, square roots, or matrices, go to WolframAlpha and type in your expression in ascii; you’ll see nicely formatted <span style="background-color: rgba(255, 255, 255, 0);">output.</span></div><div><br></div><div>Which is all to say, if you want pretty graphics in your code, all you need is a better front end. The backend can — and in absence of a better argument, should — remain unchanged.</div><div><br>On Aug 29, 2017, at 3:38 PM, John Pratt via swift-evolution <<a href="mailto:swift-evolution@swift.org">swift-evolution@swift.org</a>> wrote:<br><br></div><blockquote type="cite"><div><div dir="ltr">The case I am making is that matrix multiplication would greatly benefit.<div><br></div><div>If by typing "matrix()" a real algebra matrix popped out of code with multiple columns</div><div>spanning multiple rows of text, wouldn't that be a major improvement for everyone who</div><div>does math or graphics? There are a lot of these things.</div><div><br></div><div>Graphical elements acting as code can do much more than plain text formatting</div><div>of any programming language's syntax.</div><div><br></div><div><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Aug 29, 2017 at 1:38 PM, Adrian Zubarev 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>I still would prefer ligature fonts (Fira-Code). All these complicated characters might be good and so but remeber there are more than one keyboard layout on this planet, some of those are far more complicated than the English keyboard layout. Even I struggle sometimes with simple {} and [] because these characters are not visible on my German keyboard layout at all.<span class="HOEnZb"><font color="#888888"><br> <br><div class="m_5328321512662431125bloop_sign"><div style="font-family:helvetica,arial;font-size:13px">-- <br>Adrian Zubarev<br>Sent with Airmail</div></div></font></span><div><div class="h5"> <p class="gmail_quote" style="color:#000">Am 29. August 2017 um 18:27:05, Félix Cloutier via swift-evolution (<a href="mailto:swift-evolution@swift.org" target="_blank">swift-evolution@swift.org</a>) schrieb:</p> <blockquote type="cite" class="gmail_quote"><span><div style="word-wrap:break-word"><div></div><div>
<div>If all the hard symbols are automatically converted
by the editor, why can't the editor show you a "pretty" view and
save as "regular" text? Why does it need compiler involvement if
the problem can entirely be addressed in UI space?</div>
<br>
<div>
<blockquote type="cite">
<div>Le 29 août 2017 à 06:14, John Pratt via
swift-evolution <<a href="mailto:swift-evolution@swift.org" target="_blank">swift-evolution@swift.org</a>> a écrit :</div>
<br class="m_5328321512662431125Apple-interchange-newline">
<div>
<div style="word-wrap:break-word">
<div>Hi Chris: Please read the article that I originally
posted and mailed to the Swift team</div>
<div>before shooting down what I said:</div>
<div><br></div>
<div><a href="http://www.noctivagous.com/nct_graphics_symbols_prglngs_draft2-3-12.pdf" target="_blank">http://www.noctivagous.com/<wbr>nct_graphics_symbols_prglngs_<wbr>draft2-3-12.pdf</a></div>
<div><br></div>
<div>Alan Kay’s FONC project rewrote entire projects in
far less code by</div>
<div>using symbols in the Maru and Nile programming
languages. Alan Kay, as you know,</div>
<div>is the father of Smalltalk. Unicode symbols can
be very powerful.</div>
<div><br></div>
<div><br></div>
<div><br></div>
<div><br></div>
<div><br></div>
<br>
<div>
<blockquote type="cite">
<div>On Aug 29, 2017, at 12:28 AM, Chris Lattner
<<a href="mailto:clattner@nondot.org" target="_blank">clattner@nondot.org</a>> wrote:</div>
<br class="m_5328321512662431125Apple-interchange-newline">
<div>
<div style="word-wrap:break-word"><br>
<div>
<blockquote type="cite">
<div>On Aug 28, 2017, at 9:58 PM, John Pratt via
swift-evolution <<a href="mailto:swift-evolution@swift.org" target="_blank">swift-evolution@swift.org</a>> wrote:</div>
<br class="m_5328321512662431125Apple-interchange-newline">
<div>
<div style="word-wrap:break-word">
<div>I think the editor would recognize that "<==“ was
just</div>
<div>typed and replace it with the unicode character ≤
immediately.</div>
<div><br></div>
<div>Likewise, x^2 would be recognized and turned into x
with 2 in superscript.</div>
<div><br></div>
<div>As for how the UI would work for other types of
symbols,</div>
<div>there are all kinds of techniques for that.
That is a UI issue,</div>
<div>for a UI design team to address. XCode’s code
completion is just one</div>
<div>example of how UI can manage input issues.</div>
</div>
</div>
</blockquote>
<br></div>
<div>There is no reason to change the language to enable
this. Editors could do this automatically.
Alternatively, you could just use a programming font with
ligatures for operators, see e.g.:</div>
<div><a href="https://medium.com/larsenwork-andreas-larsen/ligatures-coding-fonts-5375ab47ef8e" target="_blank">https://medium.com/larsenwork-<wbr>andreas-larsen/ligatures-<wbr>coding-fonts-5375ab47ef8e</a></div>
<div><a href="https://github.com/tonsky/FiraCode" target="_blank">https://github.com/tonsky/<wbr>FiraCode</a></div>
<div><a href="https://www.hanselman.com/blog/MonospacedProgrammingFontsWithLigatures.aspx" target="_blank">https://www.hanselman.com/<wbr>blog/<wbr>MonospacedProgrammingFontsWith<wbr>Ligatures.aspx</a></div>
<div><br></div>
<div>-Chris</div>
<div><br></div>
<div><br></div>
<br></div>
</div>
</blockquote>
</div>
<br></div>
______________________________<wbr>_________________<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" target="_blank">https://lists.swift.org/<wbr>mailman/listinfo/swift-<wbr>evolution</a><br></div>
</blockquote>
</div>
<br>
______________________________<wbr>_________________<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" target="_blank">https://lists.swift.org/<wbr>mailman/listinfo/swift-<wbr>evolution</a><br></div></div></span></blockquote></div></div></div><br>______________________________<wbr>_________________<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/<wbr>mailman/listinfo/swift-<wbr>evolution</a><br>
<br></blockquote></div><br></div>
</div></blockquote><blockquote type="cite"><div><span>_______________________________________________</span><br><span>swift-evolution mailing list</span><br><span><a href="mailto:swift-evolution@swift.org">swift-evolution@swift.org</a></span><br><span><a href="https://lists.swift.org/mailman/listinfo/swift-evolution">https://lists.swift.org/mailman/listinfo/swift-evolution</a></span><br></div></blockquote></body></html>