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

Current state (2026-10-14)

Audited against usvm main at 19866c959d.

JacoDB represents Symbol types and intrinsic Symbol.iterator identity for native iteration. USVM still has no general Symbol input/runtime-kind/equality/coercion model.

Remaining acceptance boundary

Implement Symbol value/input identity, typeof symbol and numeric TypeError behavior without conflating symbols with references or strings. Keep intrinsic iterator identity as an existing narrow capability.

Original report and acceptance context, retained for traceability

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 天 21 小時
30 天內合併 PR
88

環境準備

這個專案沒有提供開發容器、Dockerfile 或貢獻指南,環境需要你自己搭建:先看它的 README,通用步驟見我們的新手貢獻指南。

從這裡開始

  1. 先讀完整個 Issue,再讀專案的貢獻指南。
  2. 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
  3. Fork 儲存庫,在一個分支上完成修改。
  4. 送出 Pull Request,並在描述裡引用這個 Issue 編號。

UnitTestBot/usvm 的其他 Issue

查看 UnitTestBot/usvm 的全部 Issue

相似的 Issue

更多 Kotlin Issue

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。