@Adám /⍨ also seems to be broken

@lirtosiast True, but that is because I can't replicate the hybrid function/operator behaviour. Had to go with operator so +/ would work, but then / can't be the operand of another operator. ¯\_(⍨)_/¯

@lirtosiast I really don't like NARS's approach, as it essentially introduces multi-char primitives à la J. If I could start over, I would have used monadic <≤≥>instead of ⊂⊆⊇⊃ so the latter could retain their mathematical meanings (and partition would have needed another symbol).

@Adám Isn't it limiting to stick with single-char primitives? Sure, APL has synergy between the primitives it has, but it's already almost out of bytes / keyboard space

@lirtosiast Yes it is limiting, but that is part of the beauty, that APL can put so much power into such a small vocabulary. Look at K, it has an even smaller vocabulary (but does have a couple of bi-glyphs) and still gets by quite fine. I also find that there is a huge drop in readability and memorability when going to bi-glyphs. I'm not sure why, but it may be the inability to make 1:1 (or occasionally 1:2) associations of figure to concept.

Hey @Adám, does Extended implement every pco function? I thought I saw it on the repo a while ago but all I can find now is ⍭

Yeah apparently ⍭ is pco without the one functionality I needed >.>