Hacktoberfest 2026：メンテナが10月に向けて印を付けた、オープンで初心者向けの issue。 Hacktoberfest の issue を見る

[TS PBT] Challenge context-scoped observed function summaries during symbolic search

オープン
  • 何か問題がありますか？
#403 コメント 0 件 リアクション 0 件 担当者 0 名 GitHub で見る

メンテナーはふだん 1 日以内に返信

まだ誰も着手していません。

評価

難易度
5/5
見積もり時間
1週間以上
初心者へのやさしさ
30/100
issue の種類
機能追加
明瞭さ
おおむね明確
活発さ
活発
技術スタック
kotlin, typescript
領域
devtools, testing-qa

調査の方向性

Start by reading the completed core contracts from #355 and the assessment required by #405, then inspect the existing call-policy implementation and the work in #397/#398. Define a separately identifiable extension configuration and compare it with the extension disabled. Done means a context-specific helper relation is challenged and refined or refuted, misuse and stale or side-effecting cases are covered, and results are reported separately through #357.

索引モデルが issue の本文から書いたものです。

説明

Implementation child of #345 and a required stage-two bounded extension. Owns helper-summary integration with the completed #355 core; it is not a core completion blocker. Builds on #397/#398 and the existing call-policy implementation; do not reopen or duplicate the TS Calls experiment in #360/#385.

Delivery stage

This is a stage-two extension of #345. Complete and record the core assessment in #405 before accepting this extension's end-to-end integration and results. Literature, interface design and focused experiments may start earlier; the extension never blocks #355 or #405.

Reuse the completed core contracts. This issue owns any extension-specific changes to observation, binding, scheduling, replay, shrinking and feedback integration, with focused follow-up PRs; do not retroactively broaden #351/#352 or require already completed core issues to reopen. A negative or inconclusive pilot is recorded honestly and informs design; it does not silently cancel this full-roadmap obligation.

Publish a separately identifiable extension configuration and evaluate it against the same original oracle with the extension disabled. Its final held-out evaluation belongs to #357 and is reported separately from the development pilot.

Goal

Test whether property-relevant observations at internal call boundaries can improve interprocedural search without promoting sampled behavior to a trusted universal contract.

Scope

  • Implement a bounded subset of deterministic pure helpers with supported scalar/collection-length relations. Record callee/source hash, call site, caller/property context, input support and observed result relation.
  • Derive summaries from original-runtime observations through #397. Preserve alias/mutation/read dependencies by restricting unsupported cases explicitly; do not model side-effecting helpers as pure.
  • Primary use: prioritize call contexts and generate counterexample goals to a summary at the real helper implementation via #398.
  • Evaluate speculative summary substitution only as an isolated explicit mode. It must carry assumptions into every candidate, have original-runtime replay and a budgeted no-summary search path. It cannot prove absence of bugs or justify marking paths infeasible.
  • Refine/invalidate summaries with replay counterexamples and source/context changes. Keep different call contexts separate; one context's evidence cannot constrain another without justification.
  • Reuse existing TS call models/policies and record them in configuration. Hold these policies constant across PBT-feedback comparisons so gains are not attributed to unrelated semantic-model improvements.

Definition of Done

  • At least one context-specific helper relation is observed, challenged in USVM and refined or concretely refuted.
  • A fixture detects misuse across call sites or outside observed input support; side effects and stale revisions are explicit.
  • Required challenge/prioritization mode works without trusting summaries as hard contracts.
  • #357 measures whether context-scoped summaries add to entry-only relations, including cost and misleading-summary cases. Speculative substitution may be rejected by evidence, with the negative result retained.
主要言語
Kotlin
スター
33
フォーク
27
平均マージ
3日 8時間
マージ済み PR（30日）
7

環境構築

このプロジェクトには開発コンテナ、Dockerfile、コントリビューションガイドがありません。まず README を読み、一般的な手順ははじめてのコントリビューションガイドを参照してください。

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

UnitTestBot/usvm のほかの issue

UnitTestBot/usvm の issue をすべて見る

似ている issue

Kotlin の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。