# Returning to an old hobbyhorse: Migrating higher order function names to comply with API guidelines

**URL:** <https://forums.swift.org/t/returning-to-an-old-hobbyhorse-migrating-higher-order-function-names-to-comply-with-api-guidelines/37728>\
**Category:** Pitches\
**Created:** [June 18, 2020, 10:42pm UTC](https://forums.swift.org/t/returning-to-an-old-hobbyhorse-migrating-higher-order-function-names-to-comply-with-api-guidelines/37728 "2020-06-18T22:42:03Z")\
**Posts on this page:** 1\
**Showing post:** 17

<div class="post-metadata">

**Author:** ![Douglas\_Gregor](https://sea2.discourse-cdn.com/swift/user_avatar/forums.swift.org/douglas_gregor/32/1362_2.png) [@Douglas\_Gregor](https://forums.swift.org/u/Douglas_Gregor)\
**Post date:** [June 19, 2020, 6:00pm UTC](https://forums.swift.org/t/returning-to-an-old-hobbyhorse-migrating-higher-order-function-names-to-comply-with-api-guidelines/37728/17 "2020-06-19T18:00:30Z")

</div>

> [@Chris\_Lattner3](#):
>
> I would love to see this. I don't think this needs to be a breaking change at all - we can introduce the new names, and use an (oft-speculated about, but never actually proposed) new attribute on the old names to hide them from code completion - without actually removing them. Such an attribute would be useful on other things, e.g. the initializers implementing the requirements for the LiteralConvertible protocols.

This seems pretty firmly against the spirit of the [principle of source compatibility](https://forums.swift.org/t/principles-for-trailing-closure-evolution-proposals/37265) 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.

Doug

---

_[View the full topic](https://forums.swift.org/t/returning-to-an-old-hobbyhorse-migrating-higher-order-function-names-to-comply-with-api-guidelines/37728)._
