-
We need to refactor the lexer and parser to remove some possible syntax. Plus, we could handle these literals as arrays of simpler types directly in the parser so that at the end of compilation, we ge…
-
Reference: https://v8.dev/blog/scanner and https://v8.dev/blog/preparser (and probably others in the blog page)
Has some nice ideas on optimizations for the scanning and parsing phases.
-
This module is getting complicated. So far I've avoided using lexers and parsers to keep things simple.
However, I think it's time we dive into [these advanced concepts](https://en.m.wikipedia.org/wi…
-
# Steps to reproduce:
```
from jsonpath_ng.ext import parse
import json
dat = json.loads('[{"specialKey": 5, "value": 8}, {"otherKey": 87}, [{"specialKey": 123, "value": 12}], {"olderStuff": [{"…
-
- [ ] Rename `debug` and friends to `dbg` etc.
- [ ] Rename `Logger.debug1` to `Logger.debug`
- [ ] Update doc.flix.dev
-
# Suggestion
## 🔍 Search Terms
- JavaScript return never
- JavaScript method return never
- JavaScript override method return never
- JavaScript abstract method return never
## ✅ V…
-
Immediate token rules are not considered invalid when an extra token is generated by the scanner.
Grammar:
```js
module.exports = grammar({
name: "external_extra_tokens_imm",
externals:…
-
## Parent issue
- #5678
## Issue
`RHS_DRL_END` detection is complicated. We need to find the best way for maintainability.
Parser rule is better than Lexer Island mode?
-
> After I complete this, I want to write a parser for context free grammars that couples with this scanner so that I can generate scanner/lexer functions for regular expressions and perl-style regular…
-
I'm making use of `Extras` to keep track of current line information, and in my parser I also want to `peek` the next token.
The trouble is that if I wrap the `Lexer` using `Peekable` then I no lo…