Re: [swift-users] Migrating to Swift 3 using Xcode fails

> 6. It’s still using the old compiler and my code fails to build. Select your target. Click on the Build Settings Tab. Scroll down to the Swift Compiler - Version group and change Use Legacy Swift Language Version from Yes to No. I haven’t a clue if that will actually work. It’s worth a

Re: [swift-users] Swift Playgrounds Not Included with iiOS 10.0.1 GM

And for anyone still wondering -- my iPad hadn't started but aborted the upgrade. I was still running the beta not the GM -- E > On Sep 8, 2016, at 6:16 PM, Jordan Rose via swift-users > wrote: > > The Swift Playgrounds app is not part of the Swift Open Source

Re: [swift-users] Migrating to Swift 3 using Xcode fails

I ​ am confused with your situation. You said, "I’ve migrated one of my projects to Swift 3 previously, with an earlier beta of Xcode.". Then in Xcode should not using Swift 2.3. Assuming ​X ​code using 2.3 wrongly, you should use Xcode migration tool again, after that Xcode will use Swift 3.0.

Re: [swift-users] Migrating to Swift 3 using Xcode fails

I am aware that there were new proposals, and I’ve been following along and manually migrating. The errors are due to Xcode using the Swift 2.3 compiler, which doesn’t like the new Swift 3 syntax (for example, it’s complaining that it can’t find the new types that have the NS- prefix dropped).

Re: [swift-users] Swift 3 (Xcode 8 GM) issue with @escaping

Michael any ideas about how to deal with the following? It seems like at least a bug in the fix-it. I assume I should open a bug on this? -Shawn On Wed, Sep 7, 2016 at 9:16 PM Shawn Erickson wrote: > I seem to have hit a possibly related @escaping issue... > > The following

Re: [swift-users] Swift Playgrounds Not Included with iiOS 10.0.1 GM

The Swift Playgrounds app is not part of the Swift Open Source project, but just to clear things up: the app will be in the App Store when it goes live, not shipped with the OS (as mentioned in http://www.apple.com/swift/playgrounds/). More detail than that isn't really something we can talk

Re: [swift-users] Swift Playgrounds Not Included with iiOS 10.0.1 GM

My iPad has. 81 GB free, so that wasn't the issue. Like Zhao, I used the OTA for this upgrade. I could test it by installing the restore image, but at this point I am not sure it is worth any more effort. What do you think? > On Sep 8, 2016, at 7:53 PM, Zhao Xin wrote: > >

Re: [swift-users] Swift Playgrounds Not Included with iiOS 10.0.1 GM

It is not on mine after upgrading to GM through OTA. Mine free space is 9.35GB. I think it can be easily explained. It is not a system app, it appeared in beta just because it is easily for us to test. It will appear in App Store when iOS 10 officially released. Zhaoxin On Fri, Sep 9, 2016 at

Re: [swift-users] Swift Playgrounds Not Included with iiOS 10.0.1 GM

It is still on my iPad. As far as I can tell (going by Twitter replies), if you had sufficient space for the upgrade (I had about 3.5 gb), it was not removed. I recommend filing a bug report at bugreport.apple.com -- E > On Sep 8, 2016, at 3:23 PM, Michael

[swift-users] Swift Playgrounds Not Included with iiOS 10.0.1 GM

This is just a heads-up for all who might be using/enjoying/playing with Swift Playgrounds on the iPad; it has apparently been removed from the GM that was released yesterday. There are a couple posts about it in the Apple forums, but no definitive answers have been posted as yet. I searched in

[swift-users] Migrating to Swift 3 using Xcode fails

Hi, I’ve migrated one of my projects to Swift 3 previously, with an earlier beta of Xcode. However, after downloading the GM seed, hundreds of errors pop up in my code, since it appears that Xcode has somehow reverted the compiler back to 2.3. Manually migrating using Edit>Convert>To Current

Re: [swift-users] Weak references in generic types

> On Sep 8, 2016, at 6:28 AM, Karl Wagner via swift-users > wrote: > > It is in some sense a language limitation that we cant express what you're > talking about. If we weren't using mailing lists it would be easier to search > for "protocol self-conformance" on

Re: [swift-users] Swift 3 (Xcode 8 GM) issue with @escaping

> On Sep 7, 2016, at 6:50 PM, Jacob Bandes-Storch wrote: > > On Wed, Sep 7, 2016 at 5:54 PM, Michael Ilseman via swift-users > > wrote: > I implemented a better (i.e. correct) diagnostic message for this at >

Re: [swift-users] Weak references in generic types

What I'm trying to say is that P is a protocol and not a class, so it does not conform to AnyObject. P does not conform to P. It is in some sense a language limitation that we cant express what you're talking about. If we weren't using mailing lists it would be easier to search

Re: [swift-users] UnsafeMutablePointer Swift 3 conversion

Andrew, Thank you for the compliment ;) And thank you for the 2 advices And the question about use of size or stride ? I understand that the underlaying float data are aligned in this specific case, but I wonder in fact if the shader compiler align memory the same way the swift compiler do, I