keybuk

An important goal in Swift is clarity at the point of use, this appears in the API Design Guidelines as a fundamental, but also pervades the design of the Swift language itself.

I think that removing the where clause from Swift's for loops reduces clarity.

It may be that there are other ways to express the same code result, but "only one way to do it" has never been a Swift goal that I'm aware of, and an identical result does not necessarily equate to an identical intent.

Consider the following, which was actually a source of brief confusion for me while reading some of your code.

Example 1:

rainypixels

/*
 Swift Programming Language Guide
 "A Swift Tour" Solutions
 https://developer.apple.com/library/prerelease/ios/documentation/Swift/Conceptual/Swift_Programming_Language/GuidedTour.html#//apple_ref/doc/uid/TP40014097-CH2-XID_1
 
 These are the solutions to all the "experiments" in the pre-release Swift Programming Guide 
 (released on the same day Apple announced Swift). A couple of things worth noting:
 
 1. Swift syntax, e.g. array declarations, has changed since I releasd these. So this code will 
    probably cause some errors when you paste it into a playground. Should be easy enough to fix