I was busy using NSURLProtocolClient's URLProtocol function:
welf?.client?.URLProtocol(welf!, didReceiveResponse: operation.response, cacheStoragePolicy: NSURLCacheStoragePolicy.NotAllowed)
I was expecting it to return Void. But to my surprise it returns Void?
Why is it necessary to make a distinction between Void and Void?
I have read that Void is a type alias for the empty tuple type. So, does this have something to do with a distinction between the empty tuple type vs nil?
{ some?.call() }and Swift complained since the receiving parameter was expecting a function of type() -> ()but that closure had an implicit type of() -> ()?. I finally casted the closure to() -> ()but I don't know if this is correct.