Skip to content

[TS PBT] Filter entry relations implied by declared numeric domains - #544

Open
CaelmBleidd wants to merge 1 commit into
caelmbleidd/pbt-numeric-challengesfrom
caelmbleidd/pbt-domain-relation-filter
Open

CaelmBleidd wants to merge 1 commit into
caelmbleidd/pbt-numeric-challengesfrom
caelmbleidd/pbt-domain-relation-filter

Conversation

@CaelmBleidd

Copy link
Copy Markdown
Member

Observed entry relations can repeat guarantees already supplied by input domains. For example, left <= right adds no information when left ranges over [0, 1] and right over [2, 3]. Separate these sampled relations into domainImpliedRelations, retaining their original evidence, so they no longer enter the focused-search candidate list.

The filter applies only to adapter-owned ENTRY_ARGUMENT snapshots from #543. Hand-labelled arguments and computed values remain eligible. It handles integer, binary64 and numeric constant domains, preserves JavaScript NaN/signed-zero/infinity semantics, and retains contradictions and incomplete evidence. Arbitrary preconditions and original-property formulas are not analysed. This is a narrow part of #397, not completion of inference or the feedback campaign.

Validation: 11 domain-filter tests, 16 existing inference tests and 8 real FastCheck capture/focused-search tests passed across focused runs on JDK 11 / Node 22. Strict PBT Detekt main/test passed. The functional fixture confirms that a domain-implied relation remains auditable and cannot start focused search; it is not performance evidence.

Depends on #543; the PR base is caelmbleidd/pbt-numeric-challenges, so its diff contains only the domain-filter slice.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant