Writing `eol | eoi` generates `x4::alternative` parser, which is quite overkill. Providing a dedicated parser `eol_or_eoi` would reduce compilation cost significantly. `eol | eoi` is a *very* frequently used combination; here's a screenshot from my work: <img width="534" height="464" alt="Image" src="https://github.com/user-attachments/assets/6ac60bc9-b126-4b38-978e-87e669771c4c" />
Writing
eol | eoigeneratesx4::alternativeparser, which is quite overkill. Providing a dedicated parsereol_or_eoiwould reduce compilation cost significantly.eol | eoiis a very frequently used combination; here's a screenshot from my work: