Characterize static evaluation semantics - #163
Merged
Merged
Conversation
uriahf
marked this pull request as ready for review
August 21, 2026 10:20
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.
Goal
Implement Stage 1A of the cross-language semantic audit as characterization tests only.
Coverage
Adds focused tests for:
The tests use the Stage 0 vocabulary while deliberately recording the current R representation: model-labelled shared-outcome inputs use
model, paired/multi-population inputs usepopulation, and reference ownership changes by output.Scope
Test-only. No statistical calculations, public APIs, production behavior, plotting code, package metadata, generated documentation, or
rtichoke_vizare changed.Any surprising current behavior is characterized rather than fixed in this PR.
Paired PR
Python: uriahf/rtichoke_python#365