<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div class="">Although I would personally never, ever want to do this, I see no reason why this character shouldn’t be allowed for an operator.</div><div class=""><br class=""></div><div class="">The question is: if we are to touch this are and extend the Unicode ranges of characters allowed for operators, what else is missing? A wider proposal to fill in the blanks would probably make sense.</div><div class=""><br class=""></div><div class="">
<div class="">— Radek</div>
</div>
<br class=""><div><blockquote type="cite" class=""><div class="">On 17 Dec 2015, at 21:14, Ethan Tira-Thompson 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=""><meta http-equiv="Content-Type" content="text/html charset=utf-8" class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div class="">Hi swift-evolution,</div><div class=""><br class=""></div>I wanted to use ‘·’ as a dot-product operator, but it’s not currently defined as an operator character. (<a href="rdar://problem/23930008" class="">rdar://problem/23930008</a> suggested I come here for comment.)<div class=""><br class=""><div class="">Note that dot operator (⋅, U+22C5) is already available for operators and semantically appropriate, but Mac users can conveniently type option-shift-9 to get the middle dot which is a nice feature and consequently it’s more well-known. FWIW, we have U+00B6 (¶) already defined as an operator, this would extend its range by one.</div></div><div class=""><br class=""></div><div class="">Thoughts?</div><div class=""><br class=""></div><div class="">Thanks,</div><div class=""> -Ethan</div>
<img src="https://u2002410.ct.sendgrid.net/wf/open?upn=4hhvaxvZNsLrnZM9llg93kxoqfFYC8lhv8HAehOIDqKPWFnfNDOOU4qvJ-2FzFH06fdu9vCWebEWRR0FVrA5K9G93kvhyRPMrJoaIxttBQQ7Y2tYlmnGQnbsRAL7Ql3Ep6zNfzLsSUX1gFaXjxZKdJY0Q5cohFxXNAq5qAJ-2F-2F-2FzSSzP-2BuYqdgYn1vzHcsS1V4-2FRpwtDSnNozopAA21ef0ViJI3rgV0zbTWfuSktd8W1I0-3D" alt="" width="1" height="1" border="0" style="height:1px !important;width:1px !important;border-width:0 !important;margin-top:0 !important;margin-bottom:0 !important;margin-right:0 !important;margin-left:0 !important;padding-top:0 !important;padding-bottom:0 !important;padding-right:0 !important;padding-left:0 !important;" 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=""></body></html>