lark-parser / lark-parser/lark
Where is the lexer_callbacks on this recipe?
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 6k
- Forks
- 523
- Avg merge
- 3d 22h
- Merged PRs (30d)
- 2
Description
https://lark-parser.readthedocs.io/en/latest/recipes/
The recipe 2, is ok as it uses the lexer callback.
On this commit https://github.com/lark-parser/lark/commit/1815bd7fbda932933fed604579e955a8c4d7c021 I see you added # TODO Deprecate lexer_callbacks?
Why remove this feature? Well the same thing can be accomplished now when can transform tokens with transformer. But unless it has a negative side effect as reduce performance of the parser, then, we could keep it.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the recipes page and recipe 2, then inspect commit 1815bd7fbda932933fed604579e955a8c4d7c021. Compare lexer_callbacks with transforming tokens through a transformer, including any stated performance or compatibility effects. Done would require a maintainer decision on whether the feature remains supported and a corresponding resolution for the recipe or API guidance.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- compilers
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100