nushell / nushell/new-nu-parser
Lexing error of string interpolation
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 34
- Forks
- 11
- PR merge metrics
- No merged PRs in 30d
Description
$"(')')"
Token3 0: DqStringInterpStart span: 0 .. 2 '$"'
Token3 1: StrInterpLParen span: 2 .. 3 '('
Token3 2: Eof span: 9 .. 9 ''
Lexing error. Error: Spanned { item: Generic, span: Span { start: 3, end: 4 } }, '''
$"("foo")"
Token3 0: DqStringInterpStart span: 0 .. 2 '$"'
Token3 1: Eof span: 11 .. 11 ''
Lexing error. Error: Spanned { item: UnmatchedStrInterpLParen, span: Span { start: 2, end: 3 } }, '('
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 by reproducing both interpolation examples through the lexer and inspect the string-interpolation handling that produces the shown tokens and errors. Determine the expected tokenization for nested parentheses and quoted text, then add or update lexer coverage so both examples handle their delimiters consistently without a lexing error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- compilers
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 42/100