A brace inside an f-string interpolation comment silently changes the resulting value
I maintainer di solito rispondono entro 1 giorno
Nessuno ha ancora preso questa issue.
Valutazione
- Difficoltà
- 3/5
- Tempo stimato
- 1-2 giorni
- Idoneità per principianti
- 76/100
Direzione di ricerca
Start in src/lexer.c at the interpolation boundary scanner around lines 399 and 422, then read the comment and f-string rules in docs/SPEC.md. Reproduce the issue and compare it with the existing #334/#344 quoted-character cases. Add regression coverage for braces in comments, preserving nested braces and quoted # or braces, and verify the evaluated output is exactly 3\n.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Descrizione
A closing brace inside an f-string interpolation's comment terminates interpolation before the comment ends. The program succeeds but treats the remaining expression as literal text, changing its value.
Reproduce
Save and run this exact two-line program:
print of f"{1 # }
+ 2}"
Actual: exit 0, empty stderr, stdout shown as an escaped string:
"1\n + 2}\n"
Expected: 3\n. The } after # belongs to the comment; the actual expression is 1 + 2.
Paired control: change only the comment text from } to comment:
print of f"{1 # comment
+ 2}"
This exits 0 and prints 3\n. The ordinary parenthesized-expression control also handles the same brace-containing comment correctly:
print of (1 # }
+ 2)
It exits 0 and prints 3\n. This is not a request to introduce multiline expressions: the paired f-string control already accepts and evaluates one.
Cause and contract
The interpolation boundary scanner extracts the expression before recursively tokenizing it. It skips quoted string literals but has no comment state, and counts every exposed {/}. A } in the comment ends extraction; the following newline and + 2} become f-string literal text. The inner tokenizer recognizes the comment only after the boundary was chosen incorrectly.
The lexical contract says comments extend from # to end of line, and f-strings interpolate expressions. Boundary recognition must honor those lexical states.
Regression acceptance
- The reproducer prints exactly
3\n, matching both controls. - Test opening and closing braces within comments, including multiple brace characters.
- Retain genuine nested-expression brace handling and quoted
#/brace characters;#inside a string must not start a comment. - Assert exact output after evaluation, not parse success alone: the current defective program exits successfully.
The existing #334/#344 cases cover braces inside quoted strings, not braces inside comments. No matching open or closed report was found.
Verification
Confirmed on a fresh default release build of b91768e23c5a874a64e76e4af9ab291e6aa49983, with inherited EIGS_* variables cleared. Each reproducer and paired control was executed; no runtime or test source was changed. This is a current correctness defect, not a proposed v1 language restriction.
- Lingua principale
- C
- Stelle
- 3
- Fork
- 7
- Merge medio
- 3h 56m
- PR unite (30g)
- 102
Preparare l'ambiente
Avvia il container di sviluppo del progetto nel browser, con il tuo account GitHub.
- Include un Dockerfile o un file Docker Compose
- Ha un modello di pull request
- Leggi la guida per i contributori
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di InauguralSystems/EigenScript
-
area:lint-tooling bug
Difficoltà 2/5 1-3 ore Idoneità per principianti 88/100
InauguralSystems/EigenScript#1340 ·
I maintainer di solito rispondono entro 1 giorno
-
area:stdlib found-by:code-review kind:silent-wrong
Difficoltà 2/5 1-3 ore Idoneità per principianti 88/100
InauguralSystems/EigenScript#1338 ·
I maintainer di solito rispondono entro 1 giorno
-
area:lint-tooling found-by:critic kind:docs-drift
Difficoltà 2/5 1-3 ore Idoneità per principianti 76/100
InauguralSystems/EigenScript#1335 ·
I maintainer di solito rispondono entro 1 giorno
-
area:ci found-by:critic kind:gate-defect
Difficoltà 2/5 1-3 ore Idoneità per principianti 86/100
InauguralSystems/EigenScript#1311 ·
I maintainer di solito rispondono entro 1 giorno
-
enrolment: decide test_gc_runner_controls.py (exempt vs enrol) and whether floors need a ratchetApertaarea:gates found-by:critic kind:decision
Difficoltà 2/5 1-3 ore Idoneità per principianti 65/100
InauguralSystems/EigenScript#1280 · 1 commento ·
I maintainer di solito rispondono entro 1 giorno
Tutte le issue di InauguralSystems/EigenScript
Issue simili
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 78/100
libretro/libretro-common#233 ·
-
[Bug]: chunk_span_bounds and _validated_chunk_spans reject Pydantic models ChunkSpan and AudioFileAperta
Difficoltà 2/5 1-3 ore Idoneità per principianti 78/100
BasedHardware/omi#19047 ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 88/100
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 82/100
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 76/100
obsproject/obs-studio#13936 · 2 commenti ·
I maintainer di solito rispondono entro 1 giorno