@PaulMansour because giving errors is good, there are a couple orders of magnitude less times that'd be useful (from the already incredibly few for nulls) and a couple orders of magnitude more cases when that'd be explicitly very very horrible
(a completely pointless point, but what about 1 2 3 + ,2? In Dyalog, because history, that vectorizes the two, but it'd be ambiguous now with null extending)
@PaulMansour I meant in general useful, I see nulls as being pointless, and besides some performance edge-cases, I don't think they should exist (as a global setting, at least. opt-in would be kind of okay-ish, but APL really isn't suited for that).
@Adám imo that's just a problem of how ⍳ works and that in APL having a built-in for ⍳∘⊂ would be unheard of. it also continues teaching the wrong fact that arrOfE ⍳ E for any E works (while that'd only be true for "-strings and simple scalars)
well it does solve a problem, but my thinking is that the problem should've been solved deeper down (but that sadly probably isn't possible without breaking everything)
I think I'm reiventing the wheel multiple times over, but I want to finish this answer before I post it here for you guys to see, so I have another question: Is there a way to guarantee ⌸'s ⍺ to always be in the same order? Is grading the argument the only way?