This seems pretty firmly against the spirit of the principle of source compatibility under discussion. We have used the name map since Swift 1.0, and it is ubiquitous in Swift code, books, tutorials, answers on Stack Overflow. Changing the name of map---even slowly---antiquates all of that code for a very, very small win in naming consistency.