I like the Swift way of trying to eliminate unintended consequences wherever possible. Whenever there is a change to the language that deprecates something I have been doing for years, it forces me to rethink what I consider to be best practice. The elimination of ++,-- was the most recent time this happened.
One area where I am potentially seeing a huge potential for unintended consequences are extensions that are automatically included from external files. If I extended lets say UIView somewhere, and try to reuse code relying on said extension in a new project, I might be scratching my head for a while when my code is not compiling, and then I have to hunt for the file that introduced that extension.
My question is, what are best practices when it comes to extensions? Should each extension live in its own file? Should I group them by type?
One reason I am asking is thinking that in future iterations Swift might require implicit import statements for extensions to avoid the situation I described above. Is anyone aware of anything ruminating in the Swift community?