• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Swift Autocomplete and closures
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Swift Autocomplete and closures

  • Subject: Re: Swift Autocomplete and closures
  • From: John Tsombakos <email@hidden>
  • Date: Tue, 10 Mar 2015 14:13:44 -0400
And as an aside, when I filed the radar, I did include a SourceKit Terminated crash report - as I was testing, when I was trying to see if Xcode would autocomplete the values, when I deleted some test, I got the SourceKit crash.

On Tue, Mar 10, 2015 at 1:05 PM, Chris Lattner <email@hidden> wrote:

On Mar 10, 2015, at 9:56 AM, John Tsombakos <email@hidden> 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@hidden> wrote:

On Mar 9, 2015, at 7:10 PM, John Tsombakos <email@hidden> 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@hidden)
Help/Unsubscribe/Update your Subscription:

This email sent to email@hidden
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>)
 >Re: Swift Autocomplete and closures (From: John Tsombakos <email@hidden>)
 >Re: Swift Autocomplete and closures (From: John Tsombakos <email@hidden>)
 >Re: Swift Autocomplete and closures (From: Chris Lattner <email@hidden>)
 >Re: Swift Autocomplete and closures (From: John Tsombakos <email@hidden>)
 >Re: Swift Autocomplete and closures (From: Chris Lattner <email@hidden>)

  • Prev by Date: Re: Swift Autocomplete and closures
  • Next by Date: Re: Swift Autocomplete and closures
  • Previous by thread: Re: Swift Autocomplete and closures
  • Next by thread: Re: Swift Autocomplete and closures
  • Index(es):
    • Date
    • Thread