Re: Swift 2.0

2015-07-02 Thread lowell!
rom Apple > vis-a-vis the original Swift (1.0). Has this document been updated (for Swift > 2.0) or even a new "changes to Swift" document, or are we waiting for the > "official" release of Xcode 7, and/or a new OS X 10.11 or some such? > _

Re: Swift 2.0

2015-07-02 Thread John Tsombakos
gt; > There is (or was) a PDF you could get in the Bookstore.app direct from Apple > vis-a-vis the original Swift (1.0). Has this document been updated (for Swift > 2.0) or even a new "changes to Swift" document, or are we waiting for the > "official" release of X

Swift 2.0

2015-07-02 Thread William Squires
There is (or was) a PDF you could get in the Bookstore.app direct from Apple vis-a-vis the original Swift (1.0). Has this document been updated (for Swift 2.0) or even a new "changes to Swift" document, or are we waiting for the "official" release of Xcode 7, and/or a ne

re Swift 2.0

2015-06-29 Thread Michael de Haan 
>>> var currentValue = 1 let newNewGenerator = anyGenerator { ()->Int? in let previousValue = currentValue currentValue *= 2 return ( previousValue > 20 ) ? nil : previousValue } let newGeneratedArray = Array( newNewGenerator ) For some reason you have to spe

Re: Swift 2.0 difficulty

2015-06-29 Thread Roland King
> On 29 Jun 2015, at 14:37, Michael de Haan  wrote: > > > Hi All > I am looking at Swift 2.0. The compiler has converted the code below to the > “latest” Swift syntax. This causes the error shown. I have spent a few days > trying to get this to compile. What is confusi

Swift 2.0 difficulty

2015-06-28 Thread Michael de Haan 
Hi All I am looking at Swift 2.0. The compiler has converted the code below to the “latest” Swift syntax. This causes the error shown. I have spent a few days trying to get this to compile. What is confusing to me, is that the code, listed last (func removeAnElemen…..) does compile ( all in