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.

Sign up for GitHub

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

Jump to bottom

NSInvocation+OCMAdditions: don't retain deallocating objects. #11

Merged
merged 1 commit into from
May 22, 2022
Merged

NSInvocation+OCMAdditions: don't retain deallocating objects. #11

merged 1 commit into from
May 22, 2022

Commits on May 19, 2022

  1. NSInvocation+OCMAdditions: don't retain deallocating objects. 

    Solves erikdoe#346.
`allowsWeakReference` returns `NO` if the receiver is during
deallocation. Not retaining deallocating objects would prevent crashing
later when the retained arguments are released - including the
previously deallocated objects.
There are some classes that can never have weak references - these would
also not be retained which might limit some OCMock functionality.
    @ashdnazg
    ashdnazg committed May 19, 2022
    Configuration menu
    Copy the full SHA
    6c771c4 View commit details
    Browse the repository at this point in the history