adapted lark transformer to work with v0.12 #4499
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
ltclm
force-pushed
the
fix_lark_parser
branch
from
57dc9a9 to
fceb087
Compare
ltclm
approved these changes
Nov 29, 2024
There was a problem hiding this comment.
thank you @boecklic
had to change the base to feat_PB-1241_akhet
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In newer versions of lark (newer than 0.7.8 that we used previously)
Tokenis directly subclassingstr, previously it wasToken(Str)(https://github.com/lark-parser/lark/blame/44a20c850ea7e0945a9db663a763abdcf1f86b88/lark/lexer.py#L113). This led to a different behavior of the index operator[].