yeah, idk, I guess on one hand it makes golf more annoying to beat others of the same language (takes a while to realize one completely different approach has compatible, but not exact, output), but on the other hand the emphasis on code length doesn't seem that important
unrelated, but did the monadic Base as described in A Dictionary of APL (tokenize the input) ever appear in any dialect (I'd assume so, the Dictionary describes itself as a collection of things dialects did at the time), and why did it then disappear?
But isn't being lenient on whitespace the opposite of focusing on correctness, at least in problems where whitespace plays a large part like open.kattis.com/problems/echoechoecho?
Btw, you can't see other people's solutions, right?
Anyway, I'm really enjoying the problems. Thanks for the site :)
@PaulMansour A quick count gives me 64 fully documented I-beams, 12 undocumented ones are included on APLcart, and a further 178 are entirely undocumented.
@PaulMansour Not really. It could possibly change behaviour, but then again, so can any I-beam.
@rabbitgrowth the 14 byte sol here is an abuse, just in case it wasn't clear
@Adám this doesn't seem to do the same thing (specifically, stranded arrays are in the same string in Dictionary's ⊥ and different strings in 60⌶) but still really useful, thanks
@Adám if I guess what an i-beam does, will you tell me its number?