Re: PEP 638: Syntactic macros
"David Mertz, Ph.D." <[email protected]> Thu, 2 Feb 2023 13:23:37 -0500
| Newsgroups | gmane.comp.python.devel |
|---|---|
| Message-ID | <CAEbHw4awg-xLr9=amB5JSBT43np_E2=a_iMkpwduXfPOjQgyqQ@mail.gmail.com> |
--===============5336346779431107018== Content-Type: multipart/alternative; boundary="0000000000008c3a4f05f3bbaa71" --0000000000008c3a4f05f3bbaa71 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Thu, Feb 2, 2023 at 12:46 PM St=C3=A9fane Fermigier <[email protected]> w= rote: > https://en.wikipedia.org/wiki/Mathematical_operators_and_symbols_in_Unico= de > https://oeis.org/wiki/List_of_LaTeX_mathematical_symbols > NB: on a very basic level, I remember trying, a few years ago, to use the > Unicode "empty set" symbol as a synonym for set(), and it didn't end well= , > for several reasons, including the fact that Python didn't like it as a > variable name. > I use the `vim` conceal plugin to make some of these appear on screen while I'm editing. So, for example, when I type `set()` I see `=E2=88=85`. When = I type `all(...)` I see `=E2=88=80(...)`. Much to the chagrin of Moshe Zadka, when I type `None` I see `=E2=84=B5` ..= . because I argue that =E2=84=B5_0 really should be considered an inaccessibl= e cardinal :-). However, it never causes me problems because the files on disk are just plain old ASCII (for the most part), and the special symbols are just what my screen shows, not overloads to underlying operators. --=20 The dead increasingly dominate and strangle both the living and the not-yet born. Vampiric capital and undead corporate persons abuse the lives and control the thoughts of homo faber. Ideas, once born, become abortifacients against new conceptions. --0000000000008c3a4f05f3bbaa71 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable <div dir=3D"ltr"><div dir=3D"ltr">On Thu, Feb 2, 2023 at 12:46 PM St=C3=A9f= ane Fermigier <<a href=3D"mailto:[email protected]">[email protected]</a>&= gt; wrote:<br></div><div class=3D"gmail_quote"><blockquote class=3D"gmail_q= uote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,2= 04);padding-left:1ex"><div dir=3D"ltr"><div dir=3D"ltr"><a href=3D"https://= en.wikipedia.org/wiki/Mathematical_operators_and_symbols_in_Unicode" target= =3D"_blank">https://en.wikipedia.org/wiki/Mathematical_operators_and_symbol= s_in_Unicode</a><br></div><div class=3D"gmail_quote"><div><a href=3D"https:= //oeis.org/wiki/List_of_LaTeX_mathematical_symbols" target=3D"_blank">https= ://oeis.org/wiki/List_of_LaTeX_mathematical_symbols</a></div><div>NB: on a = very basic level, I remember trying, a few years ago, to use the Unicode &q= uot;empty set" symbol as a synonym for set(), and it didn't end we= ll, for several reasons, including the fact that Python didn't like it = as a variable name.<br></div></div></div></blockquote><div><br></div><div>I= use the `vim` conceal plugin to make some of these appear on screen while = I'm editing. So, for example, when I type `set()` I=C2=A0see `=E2=88=85= `.=C2=A0 When I type `all(...)` I see `=E2=88=80(...)`.</div><div><br></div= ><div>Much to the chagrin of Moshe Zadka, when I type `None` I see `=E2=84= =B5` ... because I argue that=C2=A0=E2=84=B5_0 really should be considered = an inaccessible cardinal :-).</div><div><br></div><div>However, it never ca= uses me problems because the files on disk are just plain old ASCII (for th= e most part), and the special symbols are just what my screen shows, not ov= erloads to underlying operators.</div></div><div><br></div>-- <br><div dir= =3D"ltr" class=3D"gmail_signature"><div dir=3D"ltr">The dead increasingly d= ominate and strangle both the living and the <br>not-yet born.=C2=A0 Vampir= ic capital and undead corporate persons abuse <br>the lives and control the= thoughts of homo faber. Ideas, once born, <br>become abortifacients agains= t new conceptions.<br></div></div></div> --0000000000008c3a4f05f3bbaa71-- --===============5336346779431107018== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline