Erez Shinan
(Edited because it was nonsense.) Well, it's possible to make Lark freeze for a minute with this: ```lark start: "a"? "b"? "c"? "d"? "e"? "f"? "g"? "h"? "i"? "j"? "k"?...
P.S. when using a-z (uncommenting s+) Lark dies, probably from a recursion error.
Btw you can run the tests locally. It should be pretty easy to set up with docker. (it only tests the basic dbs, but that's usually enough)
I don't undestand, why is `OverrideNormalizeAsString` neeeded?
Something in the implementation doesn't seem right. I'll try to find time soon to look deeper into it.
Sure, makes sense to me. Why not call it "transform_columns" instead? Sounds more descriptive.
Yes, that's a good point. It should return several solutions. I think the correct thing is to break the API, since the current behavior is broken. But that would break...
No longer relevant.
I'm not sure. But according to the docs, `(?a)` and `(?L)` are supported. Maybe the limitation changed for newer versions?