unification of tests assertion implementations in Triton-program specs - #867
Draft
skaunov wants to merge 1 commit into
Draft
unification of tests assertion implementations in Triton-program specs #867skaunov wants to merge 1 commit into
skaunov wants to merge 1 commit into
Conversation
skaunov
marked this pull request as draft
February 20, 2026 17:33
skaunov
changed the title
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
1 participant
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.
tests assertion implementations in Triton specs instances can be unified in a default implementation in the trait
ideologically this is linked to #850 but can be implemented separately
It's draft as so many important/sensitive items needs to switch on this. Hence the code itself isn't finished, but needs just a few touches.