> On Mar 10, 2015, at 9:56 AM, John Tsombakos <[email protected]> wrote: > > Thanks for the reply. I have seen that there weren't Swift related changes in > 6.2, but just wanted to add the data point - as I saw the issue in 6.1.1 and > 6.3 beta 2, but didn't have 6.2 installed to see if any editor fixes/changes > had been made. > > Hopefully this'll get fixed at some point - seems sort of a big-ish issue, > surprised I hadn't seen any other reports. (and yes, I did file a Radar)
If you’re interested in Swift progress (pun intended :), then please try out the 6.3 betas. It is significantly improved in a number of ways, so much so that bug reports against 6.1.1 or 6.2 aren’t very helpful anymore. You can get the beta even if you’re not a member of a developer program: https://developer.apple.com/xcode/downloads/ -Chris > > Thanks again. > > > On Tue, Mar 10, 2015 at 12:53 PM, Chris Lattner <[email protected] > <mailto:[email protected]>> wrote: > >> On Mar 9, 2015, at 7:10 PM, John Tsombakos <[email protected] >> <mailto:[email protected]>> wrote: >> >> Well, I just tried with the newly released Xcode 6.2, and still the editor >> does not recognize the passed in variables to the block. I’m trying to find >> another call that has a completion handler to see if it’s just this call or >> is a bigger problem. > > Hi John, > > FYI, there are no significant Swift changes in Xcode 6.2, they are all > rolling into the 6.3 betas. The only swift-related change in 6.2 is related > to nullability audits of WatchKit (which didn’t exist in 6.1.1). > > -Chris
_______________________________________________ Do not post admin requests to the list. They will be ignored. Xcode-users mailing list ([email protected]) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/xcode-users/archive%40mail-archive.com This email sent to [email protected]
