That, I think, is where we're headed. Take a look at Jonathan Shapiro's latest draft and see what you think :)<br><div class="gmail_quote"><div dir="ltr">On Sat, Oct 22, 2016 at 17:46 Matt Whiteside via swift-evolution <<a href="mailto:swift-evolution@swift.org">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" class="gmail_msg"><br class="gmail_msg"><div class="gmail_msg"><blockquote type="cite" class="gmail_msg"><div class="gmail_msg">On Oct 19, 2016, at 19:07, Jonathan Hull via swift-evolution <<a href="mailto:swift-evolution@swift.org" class="gmail_msg" target="_blank">swift-evolution@swift.org</a>> wrote:</div></blockquote><snip><br class="gmail_msg"><blockquote type="cite" class="gmail_msg"><div class="gmail_msg"><div style="word-wrap:break-word" class="gmail_msg"><div class="gmail_msg">There are a bunch of symbols in unicode which are hard to tell apart, and those are bad for recognition, and we should deal with that, but this proposal is throwing the baby out with the bathwater, then lighting the baby on fire. Honestly, I would propose we find a way to have Swift see certain classes of characters as identical. Can’t decide which of the thousand + symbols should be the one true + symbol? Have them all map to one of them. That emoji X symbol looks like X, so map it to X.</div></div></div></blockquote><br class="gmail_msg"></div><div class="gmail_msg"><br class="gmail_msg"></div><div class="gmail_msg"><div class="gmail_msg">Agreed.</div><div class="gmail_msg"><br class="gmail_msg"></div><div class="gmail_msg">I really like the option of using unicode operators in swift. Removing them would be disappointing. But I do see the problem that there are a lot of redundancies and sources of confusion if there are no restrictions. Aside from the redundancies, some other cases that I find sub-optimal are: 'top-half of integral' <span style="color:rgb(51,51,51);font-family:'Open Sans','Helvetica Neue',Helvetica,Arial,sans-serif;font-size:14px;background-color:rgb(249,249,249)" class="gmail_msg">⌠, </span><span style="color:rgb(51,51,51);font-family:'Open Sans','Helvetica Neue',Helvetica,Arial,sans-serif;background-color:rgb(249,249,249)" class="gmail_msg">and</span><span style="color:rgb(51,51,51);font-family:'Open Sans','Helvetica Neue',Helvetica,Arial,sans-serif;font-size:14px;background-color:rgb(249,249,249)" class="gmail_msg"> </span> '<font color="#333333" face="Open Sans, Helvetica Neue, Helvetica, Arial, sans-serif" class="gmail_msg"><span style="background-color:rgb(255,255,255)" class="gmail_msg">left parenthesis upper hook</span><span style="background-color:rgb(255,255,255)" class="gmail_msg"><span style="font-size:14px" class="gmail_msg">’ </span></span></font><span style="background-color:rgb(255,255,255)" class="gmail_msg"><font color="#333333" face="Open Sans, Helvetica Neue, Helvetica, Arial, sans-serif" class="gmail_msg"><span style="font-size:14px" class="gmail_msg">⎛ ; </span>these<span style="font-size:14px" class="gmail_msg"> </span>don’t really seem like symbols we want to allow as operators. Perhaps *one* general rule here, is that symbols specifically meant for 2d math expressions aren't good candidates for inclusion, at least at the present. Another difficult one, I think, are the bracket-like glyphs. </font></span><span style="background-color:rgb(255,255,255)" class="gmail_msg"><font color="#333333" face="Open Sans, Helvetica Neue, Helvetica, Arial, sans-serif" class="gmail_msg">While these would be useful in certain math and physics related code, it’s not clear at the moment how these could be used in swift, until and unless </font></span><span style="background-color:rgb(255,255,255)" class="gmail_msg"><font color="#333333" face="Open Sans, Helvetica Neue, Helvetica, Arial, sans-serif" class="gmail_msg">some kind of ‘bracket overloading’ is made possible.</font></span><div class="gmail_msg"><br class="gmail_msg"></div><div class="gmail_msg"><div class="gmail_msg">I’m in favor of what Johnathan Hull has suggested above. I’m also in favor of what some others have suggested, i.e., restricting the allowed operator symbols to some uncontroversial subset, mainly from the unicode ‘math’ category of symbols, and then possibly adding more as needed.</div></div></div></div></div><div style="word-wrap:break-word" class="gmail_msg"><div class="gmail_msg"><div class="gmail_msg"><div class="gmail_msg"><div class="gmail_msg"><br class="gmail_msg"></div><div class="gmail_msg">-Matt</div></div></div></div></div>_______________________________________________<br class="gmail_msg">
swift-evolution mailing list<br class="gmail_msg">
<a href="mailto:swift-evolution@swift.org" class="gmail_msg" target="_blank">swift-evolution@swift.org</a><br class="gmail_msg">
<a href="https://lists.swift.org/mailman/listinfo/swift-evolution" rel="noreferrer" class="gmail_msg" target="_blank">https://lists.swift.org/mailman/listinfo/swift-evolution</a><br class="gmail_msg">
</blockquote></div>