Assign actual value to a strong variable in EXP_expect. #176
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
Weak values are accessed multiple times in EXP_expect, and may be set to nil in the middle of expectation. This is revealed by expecting a weak value and turning on the CLANG_WARN_OBJC_REPEATED_USE_OF_WEAK property in the build settings.
|
Alright, this feels 👍 - I was wondering if there had been churn around this but can't find anything in the history. |
orta
added a commit
that referenced
this pull request
Oct 27, 2015
…strongly Assign actual value to a strong variable in EXP_expect.
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.
Weak values are accessed multiple times in EXP_expect, and may be set to nil in the middle of expectation.
This is revealed by expecting a weak value and turning on the CLANG_WARN_OBJC_REPEATED_USE_OF_WEAK property in the build settings.