Skip to content
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

Reason: mutableOrderedSetValueForKey and mutableSetValueForKey now re… #122

Merged

Conversation

monishsyed
Copy link
Contributor

…turns a proxy set and therefore the returned value is not a backing storage and therefore all the calls that tries to add object are forwarded it to backing storage, while setValue:forKey: will set it to an empty set

Solution: Adding the values to a real set and setting that in setValue:forKey:

…turns a proxy set and therefore the returned value is not a backing storage and therefore all the calls that tries to add object are forwarded it to backing storage, while setValue:forKey: will set it to an empty set

Solution: Adding the values to a real set and setting that in setValue:forKey:
@cnstoll
Copy link
Contributor

cnstoll commented Nov 29, 2016

When did that change? Was it iOS 10? How will that work for pre-iOS 10 versions?

@cnstoll cnstoll merged commit b305eb3 into mutualmobile:master Jan 10, 2017
@cnstoll cnstoll added this to the 1.4.2 milestone Jan 10, 2017
@monishsyed monishsyed deleted the ms-resetting-set-using-returned-proxy branch January 12, 2017 16:51
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.

None yet

2 participants