@LuisMendo is there any reason &X> doesn't work like &+ or &=? I guess the inputs are kinda ambiguous, but I had to use t!2$X> which is an extra three bytes. That's this answer.
@Giuseppe & is defined differently for each function. For + it specifies one input (and + with one input assumes a second transposed input). For X> it specifies second output. For each function, & sets the input/output spec that is second-most useful/common
(The most common should be the default)
@Mr.Xcoder Hehe. Thanks! Now I have Gandalf’s voice in my head
