Function Naming In Swift 3 — by Pablo Villar

Yesterday, I started to migrate Jayme to Swift 3. It was my very first experience migrating Swift 2.2 code to Swift 3. While it’s been cumbersome, I have to admit it couldn’t have turned out another way: Swift 3 is very different from older versions; most of the changes are abrupt, and take time to think of. The good part is that it’s for our own sake: The more Swift 3 code I write, the happier I feel. 😃

There have been many, many decisions I had to take regarding changes in code. What’s more, it’s not just about translating the code, but also dividing the whole migration process into steps, and take it little by little, patiently. Changes in code is just one of those steps.

If you have already decided to start migrating your codebases, I recommend this article as a good kickstart.

Hopefully, in a near future, I’ll write a blogpost about my experience, covering the whole process and wrapping up most of those decisions I’ve been facing. But for now, I will just focus on one of those, which I consider being the most important one so far: How to write function signatures properly.

Want to know how it was done? Check the full article http://inaka.net/blog/2016/09/16/function-naming-in-swift-3/