I’m looking at someone else’s code in Julia 1.0 and noticed they use the
∉ (not in) function, which doesn’t seem to have an ascii equivalent (e.g.
notin). I realize that it’s possible to get the same functionality by typing
! (el in set), but it reminds me of the deprecation of
@test_approx_eq in Julia 0.5 in favor of
@test a ≈ b atol=ε in Julia 0.6.
I have to say that I’m a little alarmed at the existence of unicode-only functions in base. I’ve seen people raise similar concerns in various places at various times, and the answer has been something along the lines of “get a proper coding environment that supports unicode.” I often run Julia code in a cluster environment, and having to enter unusual unicode characters into scripts and packages over ssh/vim seems unnecessarily difficult.
Is there any policy on having every function and operator in base as well as the standard library have a method name that can be easily typed on any US keyboard? This would by no means precludes also having the unicode function for notational elegance and speed in less restrictive coding environments.