Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

A brace inside an f-string interpolation comment silently changes the resulting value

已关闭
#1,252 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
3/5
预计耗时
1-2 天
新手友好度
76/100
Issue 类型
缺陷
描述清晰度
描述清楚
活跃度
活跃
技术栈
c
领域
compilers

调研方向

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.

由索引模型根据 Issue 内容生成。

描述

area:runtime-vm bug found-by:code-review kind:silent-wrong

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.

主要语言
C
星标
3
派生
7
平均合并
4 小时 15 分钟
30 天内合并 PR
106

环境准备

在 Codespaces 中打开

在浏览器里用你自己的 GitHub 账号启动这个项目的开发容器。

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

InauguralSystems/EigenScript 的其他 Issue

查看 InauguralSystems/EigenScript 的全部 Issue

相似的 Issue

更多 C Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。