Perhaps it should be opt-in, but most usage would expect a BOM is ignored.
Contributor guide
Tech stack
python
Domain
backend
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
under 1 hour
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
PythonLark basicsByte Order Mark concept
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60
Research direction
Investigate the Lark lexer (lark/lexer.py) to understand where input text is processed. The issue suggests adding an option to skip BOM, likely by checking the first bytes of the input and ignoring them if they are a BOM. Look for existing tests in the test suite related to encoding or whitespace handling. The maintainer may have indicated a preference for opt in behavior in the comments.
Skip BOM (Byte order mark) · lark-parser/lark#407 | Good First Issue
