Apple

On Mar 5, 2015, at 2:28 PM, John Tsombakos <email@hidden> wrote:
I will have to check it when I get home, that sounds plausible. However it build and runs just fine. But with all the Swift-y oddness, I'm not surprised by anything. (Of course, the SourceKit service shouldn't crash either, so...)

Thanks.
On Thu, Mar 5, 2015 at 1:54 PM, Fritz Anderson <email@hidden> wrote:
On 5 Mar 2015, at 6:24 AM, John Tsombakos <email@hidden> wrote:
I entered this line of code:
        let task = session.dataTaskWithRequest(request, completionHandler: { (myData, myResponse, myError) -> Void in



        });
and when I go to write code in the completion handler block, Xcode does not recognize the variables that are being passed in - in this case myData, myResponse and myError.

Ami I doing something wrong, or does XCode just not know how to do this?
Quincey’s advice is sound as to the coding style. Let me embarrass myself once again; I’m working my way up to total humiliation, which gets you BOGO on all Developer Programs renewals and the exemption of your choice from the app-review guidelines:

My experience is that when the compiler claims not to recognize a function parameter, it’s because something up the chain isn’t unwrapped (such as session, here).

— F

References:
	>Swift Autocomplete and closures (From: John Tsombakos <email@hidden>)
	>Re: Swift Autocomplete and closures (From: Fritz Anderson <email@hidden>)
	>Re: Swift Autocomplete and closures (From: John Tsombakos <email@hidden>)