# Mumble, mumble, functions

**URL:** <https://forums.swift.org/t/mumble-mumble-functions/23886>\
**Category:** Discussion\
**Created:** [April 29, 2019, 3:35am UTC](https://forums.swift.org/t/mumble-mumble-functions/23886 "2019-04-29T03:35:38Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![jrose](https://sea2.discourse-cdn.com/swift/user_avatar/forums.swift.org/jrose/32/408_2.png) [@jrose](https://forums.swift.org/u/jrose)\
**Post date:** [April 29, 2019, 3:26pm UTC](https://forums.swift.org/t/mumble-mumble-functions/23886/3 "2019-04-29T15:26:40Z")

</div>

This was quite a long exploration, so I admit I didn't quite read it in full, but without commenting too much on what things would look like _today,_ I'd like to link my post about why Swift moved _away_ from uniform treatment of functions as `A -> B` entities (and more specifically why parameter lists are not tuples).

> [@\[Review\] SE-0111: Remove type system significance of function argument labels](https://forums.swift.org/t/review-se-0111-remove-type-system-significance-of-function-argument-labels/3209/41):
>
> Language history, a.k.a. story time! We started out with the “perfect” model of a function type being a map from a tuple to a tuple. Different argument labels were just overloads. It really was quite a simple model, other than not having 1-tuples. Well, and variadics and default values and trailing closures didn’t make sense anywhere but in functions, but still. Very simple. (And inout. And autoclosure. And maybe a few more.) Then we hit a snag: naming guidelines. We wanted argument labels to…

---

_[View the full topic](https://forums.swift.org/t/mumble-mumble-functions/23886)._
