<html><head></head><body>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.<br> <br><div class="bloop_sign"><div style="font-family:helvetica,arial;font-size:13px">-- <br>Adrian Zubarev<br>Sent with Airmail</div></div> <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">swift-evolution@swift.org</a>) schrieb:</p> <blockquote type="cite" class="gmail_quote"><span><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div></div><div>
<title></title>
<div class="">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 class="">
<div>
<blockquote type="cite" class="">
<div class="">Le 29 août 2017 à 06:14, John Pratt via
swift-evolution <<a href="mailto:swift-evolution@swift.org" class="">swift-evolution@swift.org</a>> a écrit :</div>
<br class="Apple-interchange-newline">
<div class="">
<div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">
<div class="">Hi Chris: Please read the article that I originally
posted and mailed to the Swift team</div>
<div class="">before shooting down what I said:</div>
<div class=""><br class=""></div>
<div class=""><a href="http://www.noctivagous.com/nct_graphics_symbols_prglngs_draft2-3-12.pdf" class="">http://www.noctivagous.com/nct_graphics_symbols_prglngs_draft2-3-12.pdf</a></div>
<div class=""><br class=""></div>
<div class="">Alan Kay’s FONC project rewrote entire projects in
far less code by</div>
<div class="">using symbols in the Maru and Nile programming
languages. Alan Kay, as you know,</div>
<div class="">is the father of Smalltalk. Unicode symbols can
be very powerful.</div>
<div class=""><br class=""></div>
<div class=""><br class=""></div>
<div class=""><br class=""></div>
<div class=""><br class=""></div>
<div class=""><br class=""></div>
<br class="">
<div class="">
<blockquote type="cite" class="">
<div class="">On Aug 29, 2017, at 12:28 AM, Chris Lattner
<<a href="mailto:clattner@nondot.org" class="">clattner@nondot.org</a>> wrote:</div>
<br class="Apple-interchange-newline">
<div class="">
<div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><br class="">
<div class="">
<blockquote type="cite" class="">
<div class="">On Aug 28, 2017, at 9:58 PM, John Pratt 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 style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">
<div class="">I think the editor would recognize that "<==“ was
just</div>
<div class="">typed and replace it with the unicode character ≤
immediately.</div>
<div class=""><br class=""></div>
<div class="">Likewise, x^2 would be recognized and turned into x
with 2 in superscript.</div>
<div class=""><br class=""></div>
<div class="">As for how the UI would work for other types of
symbols,</div>
<div class="">there are all kinds of techniques for that.
That is a UI issue,</div>
<div class="">for a UI design team to address. XCode’s code
completion is just one</div>
<div class="">example of how UI can manage input issues.</div>
</div>
</div>
</blockquote>
<br class=""></div>
<div class="">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 class=""><a href="https://medium.com/larsenwork-andreas-larsen/ligatures-coding-fonts-5375ab47ef8e" class="">https://medium.com/larsenwork-andreas-larsen/ligatures-coding-fonts-5375ab47ef8e</a></div>
<div class=""><a href="https://github.com/tonsky/FiraCode" class="">https://github.com/tonsky/FiraCode</a></div>
<div class=""><a href="https://www.hanselman.com/blog/MonospacedProgrammingFontsWithLigatures.aspx" class="">https://www.hanselman.com/blog/MonospacedProgrammingFontsWithLigatures.aspx</a></div>
<div class=""><br class=""></div>
<div class="">-Chris</div>
<div class=""><br class=""></div>
<div class=""><br class=""></div>
<br class=""></div>
</div>
</blockquote>
</div>
<br class=""></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="">
_______________________________________________<br>swift-evolution mailing list<br>swift-evolution@swift.org<br>https://lists.swift.org/mailman/listinfo/swift-evolution<br></div></div></span></blockquote></body></html>