So, weird question... I accidentally left Match Whole Word on when doing a RegEx workspace search (something along the lines of .*SRF). I was hoping to get results ending "SRF". The workspace just hangs in 16.0/17.0/17.1, but seems functional in 18.0 pre-release. What changed, was it just seriously optimized? And what is the expected behavior of combining these two? (I imagine a single word ending SRF?)
@JamesHeslip with a non-functional vs fast i'd expect what changed is the algorithm (i.e. O(n^whatever) → O(n) or similar) and that's not that rare with regex impls
@JamesHeslip We fall back to non-regex when regex isn't actually needed, so 18.0 may do that in more cases than 17.1, especially since that code may have been looked at when ⍠'Regex' was added in 18.0.
Ah! I might have found the/an interaction which is breaking the alternate keyboard IME after sleep/resume cycles. I closed Remote Desktop, and Alt Gr + letter started working again. RDP client is always open long-term so that could be it.
the file has 785 columns and I tried using c ← ⎕csv 'filename' 'UTF-8' (785⍴2) to force ⎕csv into reading numbers instead of characters but I still get a WS FULL error. I'm working with the larger file now, 107MB
the smaller already works with the above without having to increase WS size
@rak1507 that's just the rules - a monadic operator will always take the operand on the left, and a dyadic one requires both (and which of the two it is is decided by the presence of ⍵⍵). (similar to how you can't do 6{⍺} for a "monadic" function)