Hey!

@LuisMendo Clearing the stack isn't necessary for the testcase usage, but it will make it slightly easier to learn and remember the command as a "reset everything" button

(and by consuming, destroy them?)

Btw, why is there a special exception in the two-input "sort based on another array" S?

"(In two-array mode, if the two input arrays are scalar the result is the same as if the second input is interpreted as dimension, corresponding to single array mode)"

If I understand correctly, it's a no-op either way, only this way it's a no-op with a restriction on the second input :/

Came across it when making this 16 byter for this question. Works except when the input is a single element array, then this exception kicks in and errors out saying 0 is not a valid dimension.

@sundar You're right, they will be reset anyway by the very function. I hadn't thought of that

@sundar What I meant (but the wording is unclear) is that there is no inconsistency between normal mode (inputs: array, dimension) and two-array mode, because the result is the same (and trivial, as you point out)

@sundar Aah. There goes my "there is no inconsistency"

So the solution would be to always interpret the scalar, scalar case as two-array rather than normal mode, right?

Good catch, BTW!

@LuisMendo Reading it back now, I can see that meaning too

@LuisMendo Thanks :)

Changed the wording to In two-array mode, if the two input arrays are scalar and the second can be interpreted as a dimension there is no inconsistency with single array mode, as the result is the same

I'll correct the other thing later

... pushed