I think, arguably, the spec for orf in Phase 2, Task 5, should return vector of vectors of strings instead, since FASTA format can potentially contain more than a single sequence.
Indeed. Today, we have :GoTo and :Return (because → really should be considered syntax, not a function proper.)
I've lately also begun to prefer ⎕OPT over ⍠ since, again, it is a systemy thingy. In fact, it currently only pertains to system functions (and .NET type casting).
Not often, but it does happen. I was also offered an APL job for about 1.5×my current salary.
@MasterQuiz OK, we can consistently repro your issue now, and have logged it as number 20416: Crash in Unicode IME after using Clipboard history to paste in text, get an error and then clicking Desktop and back in Dyalog. Thank you so much for reporting it.
For 2:2:3, if I have an one-liner but takes 2GB ws to pass the example test and a more "practical" one that makes lot of use for → and procedure style programming, should I consider submit both or the functional one would be preferred, or the answer would only be judged as valid if can pass the example tests in default setting?
@LdBeth We stress "the appropriate use of array-oriented techniques"... a one-liner solution that consumes vast resources (space or time) probably won't fair as well in judging as one that is procedural but runs using a fraction of the resources.