Skip to content

skip set elem comparison when already matched#37280

Merged
jbardin merged 2 commits intomainfrom
jbardin/assert-set-compat
Jun 27, 2025
Merged

skip set elem comparison when already matched#37280
jbardin merged 2 commits intomainfrom
jbardin/assert-set-compat

Conversation

@jbardin
Copy link
Copy Markdown
Member

@jbardin jbardin commented Jun 27, 2025

If both elements of the set have already been matched, there is no need to compare them again.
Verified the coverage using existing tests, so no need for another duplicate test case.

Closes #32940

jbardin added 2 commits June 27, 2025 09:42
If both elements of the set have already been matched, there is no need
to compare them again.
@jbardin jbardin merged commit 7b3d9bf into main Jun 27, 2025
13 of 14 checks passed
@jbardin jbardin deleted the jbardin/assert-set-compat branch June 27, 2025 15:11
@github-actions
Copy link
Copy Markdown
Contributor

I'm going to lock this pull request because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active contributions.
If you have found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jul 28, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

terraform apply of large TypeSet is slow, assertSetValuesCompatible is too complex

2 participants