@RGS Dyadic operators are 4th class citizens. They cannot be "returned", only named and applied. You can do _Each←¨ but not _Power_←⍣. Does it have to be this way? Not really.
@Adám it can for now because I only have simple parsers yet. However S is supposed to be much more general and later it will be applied to more complex functions, so I was looking for a more general solution
@ab5tract Not an oversight, just not quite got there yet. For one thing @Bubbler pointed out that 18.0 currently refers to the wrong version of RIDE, and that has led to me (a) fixing that problem and (b) working on adding zero footprint RIDE to all non-Windows installations.
@xpqz Yes, in principle, but not practically. One of my side projects for 19.0 is to move it to GitHub, and then we can take suggestions and submissions in a more orderly manner.
@xpqz spaces - ↓ ⊃¨ ,∘⊂⌸ ⊢/¨; from that its clear that there are 4 parts (each a function) - ,∘⊂⌸ gets the args of ⊃¨ and ⊢/¨, and the result is ↓ed; ,∘⊂⌸ is an idiomatic usage of ⌸ and the rest is basic APL
(right, we now have ⍥; ,⍥⊂⌸ would be more 'correct' imo even if it doesn't matter here)
@xpqz i did have to group those parts in my head, which can take a while. i find it easier to just copy-paste & add proper spaces, it gets way easier then
@dzaima There is a named function definition in BQN2NGN. For example (a‿b F c)←a-b-c. You can distinguish it from selective assignment because that has to use ↩. No reason you couldn't allow separate monadic and dyadic definitions with this form or (F⁼ x)←….
But it is kind of a weird form of assignment. The body can only be a single expression, and nothing is allowed to the left of it.
(the way this works is that (a b)(c d) is a "mutable" object, and it is composed of mutable objects, and assigning works recursively, which is already required for the a b←c case; if a and b are functions, the mutable object can't be created)
@dzaima Yes. I don't think there's a problem with val←Func, but Func↩val starts to look like modified assignment. I'm not sure there are actually any conflicts yet, but I don't want to have to worry about it when designing.