Skip to content

Restore the .concurrent option for NSArray's enumerateObjects(…) #1366

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Dec 12, 2017
Merged

Restore the .concurrent option for NSArray's enumerateObjects(…) #1366

merged 2 commits into from
Dec 12, 2017

Conversation

millenomi
Copy link
Contributor

@millenomi millenomi commented Dec 8, 2017

(Let's try this again. The previous attempt had an issue in the test for enumerateObjects(at:options:using:) where it could've set the stop flag to true before all indexes corresponding to our expectation had been set to true, which could lead it to inconsistently failing.)

NSArray implements these methods as: someIndexSet.enumerate(options: options) { block(self[$0]…) }, so the fix goes in NSIndexSet.

Includes NSArray tests.

…ethods in NSArray.

 - These methods are implemented as (relevant NSIndexSet).enumerate(options: options…), so the fix goes in NSIndexSet.

 - Includes NSArray tests.
…'re supposed to see, not until we see one that isn't supposed to be seen (because it may arrive out of order vs others we want to mark as seen.)
@millenomi
Copy link
Contributor Author

@swift-ci please test.

@millenomi millenomi requested a review from parkera December 8, 2017 22:43
@millenomi
Copy link
Contributor Author

@swift-ci Please test and merge.

@swift-ci swift-ci merged commit 7bf5fc7 into swiftlang:master Dec 12, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants