Repository navigation
[TS Calls] Build class coverage experiment infrastructure - #476
Merged
CaelmBleidd merged 3 commits intoOct 13, 2026
Merged
Conversation
CaelmBleidd
force-pushed
the
caelmbleidd/ts-calls-class-coverage-experiment
branch
from
October 13, 2026 21:57
d3c9c95 to
97f9877
Compare
CaelmBleidd
marked this pull request as ready for review
October 13, 2026 22:01
CaelmBleidd
force-pushed
the
caelmbleidd/ts-calls-class-coverage-experiment
branch
from
October 13, 2026 22:01
97f9877 to
106e4a9
Compare
CaelmBleidd
deleted the
caelmbleidd/ts-calls-class-coverage-experiment
branch
October 13, 2026 22:02
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Calls needs class-wide coverage and bounded scheduling to compare its four policies under shared 30- and 120-second class budgets. This draft adds only infrastructure missing from the existing coverage PRs; their collectors, replay, metrics and identity machinery will be reused after they merge.
Implemented increments:
CoverageZone.CLASStracks executable methods declared in the entry-point classes, including constructors and private helpers, and excludes foreign classes and bodyless declarations.TsOptions.classCoverageTargetsselects fixed target classes independently of wrapper entry points. Unknown/ambiguous targets, an explicit empty set and incompatible coverage modes are rejected. Scheduling and statistics tolerate entry points outside the tracked class scope.maxEntryPointTimeQuantumbounds CONSTANT_TIME turns while retaining pending queues across visits. A step/solver operation can overrun the requested quantum; subsequent turns recompute their bounded share of the remaining budget.removeCoveredEntryPoints = falsedisables coverage-based queue pruning for budget/exhaustion experiments. Both new options preserve existing behavior by default.Validation after integrating main at
966273114337cfc37ab17e4d3bb2d4bd26d0242c: 19 core path-selector tests and 26 TypeScript class/completion/shared-analysis/sparse-array/overload tests passed (45 tests, zero failures or skips). TypeScript Detekt main/test andgit diff --checkpassed. Core Detekt main/test reported no findings in changed files; their broader reports retain findings in untouched files.Ignoring explicit targets makes the wrapper regression fail on a result assertion: one candidate per wrapper instead of two per target class. The bounded-turn and pending-state regressions also fail on result assertions when their production changes are disabled. The previously observed CI lint issue in the combined analysis method is removed by extracting class scope selection and validating immutable options at machine construction. The two previously failing sparse-array checks pass with the already merged main fixes. A fresh full CI result is still pending.
Existing infrastructure to reuse:
Remaining class-specific increments:
No new collector or duplicate coverage runner is included. Open PRs remain separate dependencies. Updates from main include only changes the user has already merged; their infrastructure is reused. The class experiment has not been run. Design notes and experiment plans stay outside the repository diff, and each increment is published as a separate commit.