Swift 3 API changes

[phatblat]

Targeting master as it's the only branch. Do you want this in a separate swift3 branch?

[AliSoftware]

👍 yes a dedicated swift3 branch seems more appropriate

[AliSoftware]

Pulled in https://github.com/AliSoftware/Reusable/tree/swift3 👍

Thx a lot. I've added you as collaborator for the occasion (so you can create branch directly on Reusable in the future instead of needing your own fork)

[phatblat]

💃 Sweet!

[AliSoftware]

Please don't forget to add an additional commit on this new branch to:

• add an entry in the CHANGELOG.md to credit yourself
• Update the README.md with the same changes (e.g. the README references UIKit methods like registerNib and registerClass to explain the behavior, so those will need an update

Once you've done that, with your new collaborator rights you'll be able to check those checkboxes above (I think) and close the PR at last.

[EDIT] oh wait can't reopen the PR now that the branch is deleted on your fork, of course. Never mind. Just don't forget to update the README & CHANGELOG then 😉

[AliSoftware]

Just realized Reusable still doesn't have tests nor Travis integration 😱 so that PR wasn't actually tested by Travis to ensure it compiles with Swift 3… Would be about time to implement #7 so we can be sure nothing breaks at each PR!

[phatblat]

I'll open a new PR for those metadata changes. Taking a step back, should this change be using conditional compilation markers like #if swift(>=3.0)? With those this could possible live in the master branch. Although, testing each path might be more difficult, but could probably be handled with the right Travis matrix.

[AliSoftware]

Ohh right it's definitely worth adding #ifs there I think especially given the changes are quite minimal it seems.

If you do that then not sure about the README then as the PR will indeed be merged into master and code will be valid for both Swift 2+3 so probably not worth updating the references to Swift 2 APIs in the README?
But probably worth mentioning in the README that the lib is compatible with both Swift 2+3 at least then.