why art thou enlist enlist

[ryanhamilton]

Oddity from TorQ's loadf
https://github.com/DataIntellectTech/TorQ/pull/150/changes#diff-c19b7cb74dfe97c5ac97c48743ab5ce62ef9f687d0721c71c5862ce9bf77cfb2R463-R470

q)"apple" in ("qwe";"apple";"jhjg")
1b
q)"apple" in ("qwe";"orange";"jhjg")
0b
q)"apple" in enlist each ("qwe";"apple";"jhjg")
0b

The only way for torq to work is for that last line to return 1b
I can't work out why it returns 1b, if you also can't it's probably best to change it to a flat list. :)

[Papamaci444]

Looking at it - it looks to me there are just too many enlists there. We should keep loadedf as a list of strings. Maybe the author forgot that "" is already a string.
Asking the reviewers, will do a test then hopefully gets fixed quickly.
Thanks for the heads up!

[Papamaci444]

Found the reason:
https://code.kx.com/q/basics/atomic/#string-atomic
The extra enlist the code uses unnecessary, but doesn't do any harm as in just finds the strings at any depth
credits to @pkaiserq