Repository navigation
tests: add kitchen sink test - #431
Merged
apoelstra merged 2 commits intoOct 6, 2026
Merged
Conversation
Add one program that uses every language feature, built-in and unstable feature, with a regression test that compares its full encoding against test-data/kitchen_sink.json. Any compiler change that alters generated code, and so the CMR, fails this test. A separate run test executes the program so its assertions are checked too. The regression harness now loads examples/<name>.args when present, so the example can cover parameters. Assisted-by: Claude
Remind authors of language feature changes to extend the kitchen_sink example, so the CMR regression test keeps covering every feature. Assisted-by: Claude
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
2 participants
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.
Adds an example that uses all of the current language features so that we can detect changes to the generated code. We already have fuzzing to try and detect errors, but the aim here is to detect unintentional changes to CMRs.
It's not fool proof, but I've also added a PR template to try remind developers to add new features to the kitchen sink.