vc:{2<+/~^"aeiou"?x}
rp:{|/~':x} / repeat letters
il:{~|//~^("ab";"cd";"pq";"xy")?/:,2':x} / in naughty list
s051:{&/(vc;rp;il)@\:x} / all true
here's something I don't understand
2015/5.txt is just a file with strings on new lines
but when I call +/s051 'day 5
I get a rank error
but if I call +/ s051@'day5 it works just fine
I can't tell if I'm just fried and need sleep, or if I just can't make heads or tails of things today
selection, application, "spelling", iteration, its all so particular in K... idk maybe I just need some sleep
it'd really be nice if the rules were codified somewhere and not left up to tripping over yourself ever few minutes. In particular with regard to white spacing, and when user defined functions are allowed or not
@ngn so am I to understand that when we say "noun"/"verb"/"adv" we are not referring to the implied values in the evaluation of an expression but the literal tokens that comprise the text of the expression?
@nathanrogers at least in the world of apl, "array" is more general it could mean "atom" (i.e. "scalar") or "list" (i.e. "vector")
also note that terminology changed in k9 - a "list" there is only the generic list - (0 1;2 3) but not typed lists like 0 1 or "ab" (i think that was a bad move)
@nathanrogers why uppercase?
case could be used for the distinction between atom(lower) and list(upper)
@ngn nulls question, is the reaction to getting Nulls just reflexively ~^? because dealing with nulls feels like an interruption to otherwise concise expressions
what sort of common "tricks" are there for handling nulls? What are the direct use cases aside from existence or non-existence?
e.g. to make a projection. f:{x+y+z} has valence 3. calling f[1;2] returns a projection, which is a monadic function. f[1;;2] does the same and does not bind y. the arg list contains a nil.
But there are differences between nulls and nil. 0N is a null value of type int. it will not project.
i tell you though, typing simple stuff like this and seeing the screen scrawl past will never stop being satisfying
{{(,x 1),.'x 2 4}-5#" "\x}@'day 6
("toggle 461,550 through 564,900" "turn off 370,39 through 425,839" "turn off 464,858 through 833,915" "turn off 812,389 through 865,874" "turn on 599,989 through 806,993") (("toggle";461 550;564 900) ("off";370 39;425 839) ("off";464 858;833 915) ("off";812 389;865 874) ("on";599 989;806 993))
@ngn and with respect to rollback - the easiest way to do that, I think, would be to fork() on executing repl code, if need to bail out, kill the repl-code process, if finished, kill the waiting process. stuff that interacts with the real world, like network or files, would not actually be rolled back of course (and would be weird), but the copy-on-write behaviour would mean you only pay for changed memory unlike the wasm solution.
