Just to continue here our twitter discussion:

What about a custom operator version:

target.closure <= (self, other, { strongSelf, strongOther, some, args in
    // ... code
})

Are any limitation from user point of view to code completion of using Strongify ?

Just a random idea, wouldn't it be more explicit with something like that:

target.closure = strongify(weak: self, weak: other) { strongSelf, strongOther, some, arguments in
    /// ... code
}

First I thought about using guard but it's not possible:

target.closure = guard(weak: self, weak: other) { strongSelf, strongOther, some, arguments in
    /// ... code
}

hello, can you do a benchmark on build time / indexing time, so we decided to use this or not? because I see the implementation is somewhat redundant.

Thanks.

Hi it's possible about you create strongify with specific default value as return statement, when one of the context doesn't exist anymore?

https://github.com/CocoaPods/Specs/tree/master/Specs/5/0/f/Strongify

Hi, correct me if I'm missing something, but cocoapods installs version 1.1 and doesn't recognize 1.2's existence, and it looks like the master specs repo is still pointed at 1.1.