Decoupling Swift from Cocoa's Foundation about swift HOT 6 CLOSED

Yeah, I'm in favor of this. I don't remember many tests actually using Foundation, but I don't know about the examples.

from swift.

This is a good idea. We should always prefer the native Swift types over the Objective-C counterparts.

But, I think we should hold off on this until at least the official release of Swift 2.0. We'll have a lot of work to do updating tests anyway. We should probably start a thread on Swift 2 migration. Some of the changes like @testable will make things easier for us if we handle them correctly. I'm thinking that we provide a starter project along with the first exercise (as suggested in another issue) and provide instructions on how to add new exercises to that project. Then we can control the package name and make the rest of the process smooth.

I'd also like to reorder the exercises. I ran through the first few with a new group the other day and man, doing Bob second was brutal. String process was tedious, and I think we'd be better off having some quicker exercises early.

from swift.

This brings up another question:
Is there a value on keeping swift 1.2 versions of the problems around?
I can see v3 v4 of swift starting to change a lot but many people could have limitation on what they are working on ( think python 2 vs 3 ) etc.

from swift.

I think we should just ditch the 1.2 stuff when we migrate. Maintaining two sets of exercise will be a real pain, and adoption rates will probably be astronomical like they are with iOS. I think Xcode is an automatic update from the App Store.

from swift.

Sounds good.

from swift.

Swift really needs an NSDate native also Regular expression.

from swift.