3 ms·
I'm not quite sure I understand how they are applicable, since access patterns itself can be arbitrary complex For example how is github.event.pull_request.lab
by jyndbeb 1y ago
I'm not quite sure I understand how they are applicable, since access patterns itself can be arbitrary complex
For example how is github.event.pull_request.labels[another_variable].name handled?
- yorwba 1y agoSince it only needs to classify the result as one of "fixed", "structured" or "arbitrary", it doesn't matter what the value of "another_variable" is, you'll always be in the same state at the end. Finite state transducers can handle an infinite number of possibilities with a finite number of states just fine. It's a bit strange though that the author constructs the FST to only recognize a finite list of strings. Probably some of the matching logic that could have been part of the FST is pushed into the normalizer instead.
- woodruffw 1y agoAuthor here. > Probably some of the matching logic that could have been part of the FST is pushed into the normalizer instead. Yep, exactly -- there's a great deal of prenormalization that in principle could be pushed into automata run over the FST instead. The reason I didn't do that is laziness, but it's the obvious next step :-)