[Constant Evaluator][Tests] Add tests to check constant evaluability of Swift code snippets #27208
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.
This PR adds a new sil-opt pass:
ConstantEvaluableSubsetCheck.cpp
to check constant evaluability of Swift code snippets. This pass is only used in tests and will eventually replacepound_assert.swift
tests.This PR also adds a new test:
constant_evaluable_subset_test.swift
that contains Swift code snippets that are expected to be constant evaluable and those that are not. The goal of this test is to document Swift code snippets known to be constant evaluable (and not) and catch any regressions in the SILGen and mandatory passes that could change the constant evaluability of these code snippets.(See only the most recent commit in this PR, which has the relevant changes.)