Restore "enumerability" of SpecSet
#6532
Merged
Conversation
This file contains 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
github-merge-queue
bot
removed this pull request from the merge queue due to failed status checks
deivid-rodriguez
added a commit
that referenced
this pull request
Mar 24, 2023
Restore "enumerability" of `SpecSet` (cherry picked from commit 4d35dd4)
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.
What was the end-user or developer problem that led to this PR?
In #6495 I made
SpecSetno longer behave as a "sane" enumerable.What is your fix for the problem, implemented in this PR?
Since the commits that broke that were just refactoring commits not necessary for the bug fixes in #6495, I will revert them until I find time to properly address this.
Fixes #6528.
Make sure the following tasks are checked