Re: [swift-evolution] [Draft] @selfsafe: a new way to avoid reference cycles

On 20 Feb 2017, at 06:05, Brent Royal-Gordon via swift-evolution wrote: >> On Feb 19, 2017, at 7:06 PM, Matthew Johnson wrote: >> >> Often you hand it to something owned by self, but it's also the case that >> you often hand it to something

Re: [swift-evolution] [Draft] @selfsafe: a new way to avoid reference cycles

> On Feb 19, 2017, at 7:06 PM, Matthew Johnson wrote: > > Often you hand it to something owned by self, but it's also the case that you > often hand it to something not owned by self, but that should not extend the > lifetime of self. I don't agree that it shouldn't

Re: [swift-evolution] [Draft] @selfsafe: a new way to avoid reference cycles

Sent from my iPad On Feb 19, 2017, at 6:30 PM, Brent Royal-Gordon wrote: >> On Feb 19, 2017, at 6:45 AM, Matthew Johnson wrote: >> >> 1. Swift *already* acknowledges that it is far easier to create a reference >> cycle through captured strong

Re: [swift-evolution] [Draft] @selfsafe: a new way to avoid reference cycles

> On Feb 19, 2017, at 6:45 AM, Matthew Johnson wrote: > > 1. Swift *already* acknowledges that it is far easier to create a reference > cycle through captured strong references to `self` than any other way. This > is why you have to explicitly say `self.` in escaping

Re: [swift-evolution] [Draft] @selfsafe: a new way to avoid reference cycles

Thanks for reply Mathew. Here are some more comments: > On 19 Feb 2017, at 15:51, Matthew Johnson wrote: > > > > Sent from my iPad > >> On Feb 19, 2017, at 7:41 AM, David Hart wrote: >> >> I must admit I find this proposal very weird. > > I am

Re: [swift-evolution] [Draft] @selfsafe: a new way to avoid reference cycles

Hi Matthew, I'm not convinced we should come with a new mechanism that would handle the capture of `self` differently from the other captures. I do understand that this would match the way Apple APIs work, but as a general purpose language, this looks weird to add some asymmetry in the

Re: [swift-evolution] [Draft] @selfsafe: a new way to avoid reference cycles

Sent from my iPad > On Feb 19, 2017, at 7:41 AM, David Hart wrote: > > I must admit I find this proposal very weird. I am going to remove the `withWeakSelf` property. This conversion can be handled behind the scenes as an implementation detail of passing an argument to

Re: [swift-evolution] [Draft] @selfsafe: a new way to avoid reference cycles

Sent from my iPad On Feb 19, 2017, at 2:15 AM, Brent Royal-Gordon wrote: >> On Feb 18, 2017, at 5:24 PM, Matthew Johnson via swift-evolution >> wrote: >> >> This proposal introduces the `@selfsafe` function argument attribute which >>

Re: [swift-evolution] [Draft] @selfsafe: a new way to avoid reference cycles

I must admit I find this proposal very weird. • it only handles strong references to self. While the APIs we work with mostly direct us towards accidental references cycles including self in closures, I would want a compiler feature to be much more generic. • I'm not a fan of "magically" fixing

Re: [swift-evolution] [Draft] @selfsafe: a new way to avoid reference cycles

This places the burden on users. The library is not able to offer a guarantee. Sent from my iPad > On Feb 19, 2017, at 1:20 AM, Derrick Ho wrote: > > What wrong with [unowned self] >> On Sat, Feb 18, 2017 at 11:01 PM Daniel Duan via swift-evolution >>

Re: [swift-evolution] [Draft] @selfsafe: a new way to avoid reference cycles

> On Feb 18, 2017, at 5:24 PM, Matthew Johnson via swift-evolution > wrote: > > This proposal introduces the `@selfsafe` function argument attribute which > together with a `withWeakSelf` property on values of function type. Together > these features enable library

Re: [swift-evolution] [Draft] @selfsafe: a new way to avoid reference cycles

What wrong with [unowned self] On Sat, Feb 18, 2017 at 11:01 PM Daniel Duan via swift-evolution < swift-evolution@swift.org> wrote: > This reminded me of an idea I had long time ago which will have a similar > effect: add a way to disable implicit captures for closures. FWIW. > > > On Feb 18,

Re: [swift-evolution] [Draft] @selfsafe: a new way to avoid reference cycles

This reminded me of an idea I had long time ago which will have a similar effect: add a way to disable implicit captures for closures. FWIW. > On Feb 18, 2017, at 5:24 PM, Matthew Johnson via swift-evolution > wrote: > > # `@selfsafe`: a new way to avoid reference

[swift-evolution] [Draft] @selfsafe: a new way to avoid reference cycles

# `@selfsafe`: a new way to avoid reference cycles * Proposal: [SE-](-selfsafe.md) * Authors: [Matthew Johnson](https://github.com/anandabits) * Review Manager: TBD * Status: **Awaiting review** ## Introduction This proposal introduces the `@selfsafe` function argument attribute which