You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Now, maybe I'm wrong, but it seems to me that the compiler should be complaining about the bare `name`. It should be insisting that I say `self.name`. I am handling `f` in a way that will capture `self` and preserve it, and the compiler knows this, because `funcPasser` has a `@escaping` parameter. If this were an anonymous trailing closure, the compiler would insist that I say `self`, so why doesn't it insist on it here?
The text was updated successfully, but these errors were encountered:
I consider these two separate issues. The former captures self as soon as f is created; the latter has an f that's independent of any particular instance, and then partially applying it. More concretely, the self. requirement would go on name in the first example and on f in the second.
Environment
Xcode Version 8.0 beta 6 (8S201h)
Additional Detail from JIRA
md5: 5d150b756a45847a9f3a4d7cab69f1c4
relates to:
Issue Description:
Consider this:
Now, maybe I'm wrong, but it seems to me that the compiler should be complaining about the bare `name`. It should be insisting that I say `self.name`. I am handling `f` in a way that will capture `self` and preserve it, and the compiler knows this, because `funcPasser` has a `@escaping` parameter. If this were an anonymous trailing closure, the compiler would insist that I say `self`, so why doesn't it insist on it here?
The text was updated successfully, but these errors were encountered: