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

[TS] Execute Symbol values without treating them as references

未关闭
#439 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
55/100
Issue 类型
缺陷
描述清晰度
基本清楚
活跃度
活跃
技术栈
kotlin, nodejs, typescript

调研方向

Start with the sort mapping in usvm-ts/src/main/kotlin/org/usvm/machine/TsContext.kt and the typeof handling in usvm-ts/src/main/kotlin/org/usvm/machine/expr/TsExprResolver.kt. Add a focused regression for the provided Symbol example after the required Symbol EtsIR is available, then compare the supported result with a concrete Node.js replay. Done means Symbol behavior is represented explicitly, while unsupported operands or environments remain marked as approximations.

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

描述

enhancement

Problem

The symbolic machine has no Symbol value sort or runtime-kind branch; Symbol-typed values fall outside its type-to-sort mapping.

Minimal TypeScript example

export function kind(value: symbol): string {
  return typeof value;
}

Expected behavior

For a Symbol input, kind returns "symbol". Symbol equality uses identity and numeric coercion raises TypeError; do not collapse symbols into string/object/unknown reference semantics. Requires Symbol EtsIR from UnitTestBot/jacodb#379.

Current source evidence

Sort mapping; typeof cases.

Checked against USVM main 53dce8f3bca2713642c783ba8308a6a360a9e516. This exact snippet is a proposed regression from source audit; it has not yet been run as a new end-to-end test. #368 audits the existing call approximations but does not implement these individual fixes.

Acceptance criteria

  • A focused test checks the symbolic outcome without reporting an approximation as exact semantics.
  • The supported case agrees with concrete TypeScript/Node.js replay.
  • Unsupported operand or environment cases remain explicit.
主要语言
Kotlin
星标
33
派生
27
平均合并
3 天 8 小时
30 天内合并 PR
7

环境准备

这个项目没有提供开发容器、Dockerfile 或贡献指南,环境需要你自己搭建:先看它的 README,通用步骤见我们的新手贡献指南。

从这里开始

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

UnitTestBot/usvm 的其他 Issue

查看 UnitTestBot/usvm 的全部 Issue

相似的 Issue

更多 Kotlin Issue

把新 issue 发到你的邮箱

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