@dzaima Seems to be a RIDE (that's what you use, right?) issue. Doesn't happen in the Windows IDE, where \n is then just treated as a normal inline character:
@Adám each tail vector would also need to include spacing details. And in most digital forms they're either a vector of (character; page; x; y) (or similar), or a single string anways
what happens if you copy&paste the newline character?
if this is really intentional behavior, the proper thing to do would be to disallow selecting multiple lines & make pasting newlines paste the character form. (of course, doing that would be stupid, but otherwise I'm calling the windows IDE broken)
@Adám "Delimited by ". Internal quotes are written \", backslashes are written \\, newlines are written \n." Not that much worse. (ofc you can add more escapes, but ¯\_(ツ)_/¯)
I think string escape sequences is something that doesn't need to be particularly innovative and the most productive use of them would be to do what is standard in other languages
@Adám that'd require breaking backwards-compatibility of x←0, and be extremely confusing to anyone who has used any language where 0x2a would be a number
@Adám (⍬2⍴)⍫, is kind of unavoidable. inverse of ⍳ is the 4th item in my dzaima/APL TODO list (and at some point was implemented, but it didn't check for errors so was abandoned for later)
@Adám note that ⍪(1 2)(3 4) is still a bit ugly as [⊂1 2⋄⊂3 4] (and [⍮1 2⋄⍮3 4] is equivalent, so the special case only "helps" in the ⍪simpleScalarVector case, assuming ⍮ exists which it really really really really should)
@dzaima I know, but only from a stand on purity, no?
Of course, all this wouldn't have been a question if APL had a properly though out array notation from the outset, i.e. if people at IBM hadn't ignored Iverson's protests.
@dzaima He did, and yes, except we don't know how he would have disambiguated.
Ah, hang on, he used x for scalars, x for vectors, and X for matrices, so there might never have been ambiguity.
They would have been able to figure something out. Maybe allow a trailing , or something. (42,) doesn't bother me at all, while (42⋄) looks ugly to me.
Oh, wait, (,42) would work.
But of course, with nested arrays, that's problematic.
Aha.
Our pairing of ravel and catenate really doesn't make so much sense. BQN is better there.
If monadic , was instead "add leading axis", then it could work.