> parsed with the same precedence as +:
who's gonna remember that when reading code though? in practice, that'll mean
you'll end up adding parens to disambiguate, eg:
(a ⊞ (b ∤ c) ⩕ d)
Run
not only that, but precedence rules are much more complex than just considering
the 1st character
the main use case for this would be code golf/obfuscation challenges, or
replacing APL > `life←{↑1 ⍵∨.∧3 4=+/,¯1 0 1∘.⊖¯1 0 1∘.⌽⊂⍵}`
(<https://en.wikipedia.org/wiki/APL_(programming_language)>)
I'm not in a hurry to have to disambiguate between those when reading code:
a * b vs a ∗ b
⊙ vs ⦿
& vs ⅋
⋅ vs ∘ vs ⋄
⨱ vs ⨲
⋏ vs ⩑
Run
