Master doesn't compile on XCode 6.1.1 / Swift 1.1 due to default context parameters about brightfutures HOT 3 CLOSED

These are caused by Swift 1.2 overload changes in e38a69c

As you can't submit apps written with Swift 1.2 to App Store (only official XCode and GM Seed versions can be used for App Store submissions, not XCode Beta, and XCode 6.3 GM Seed will likely be available earliest in April-June), I would keep the master branch compatible with the official Swift 1.1 and have a separate 1.2 branch.

from brightfutures.

I agree that breaking Swift 1.1 support on the master branch is not good. It was a bad decision on my part, sorry about that.

It should be like you suggest: the master branch should be compatible with the latest public release of Swift, there can be branches to support a beta or a previous version (e.g. 1.1 as soon as 1.2 comes out).

I'm not sure if I'll have the time to do this soon, so feel free to start on a pull request restoring Swift 1.1 support to the master, if you want (and seem to be suggesting in #12). Thanks!

from brightfutures.

I did the minimal work for porting master back to Swift 1.1. Please review and suggest if any further changes are needed. I think it's wiser to leave setting up the swift1.2 branch to you.

And thanks for the great library. I hope to contribute in the future (pun intended).

from brightfutures.