# Dears, the Closures chapter make me Drunk!

**URL:** <https://forums.swift.org/t/dears-the-closures-chapter-make-me-drunk/73831>\
**Category:** Using Swift\
**Tags:** closure\
**Created:** [August 8, 2024, 1:54pm UTC](https://forums.swift.org/t/dears-the-closures-chapter-make-me-drunk/73831 "2024-08-08T13:54:47Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![mgstanley](https://sea2.discourse-cdn.com/swift/user_avatar/forums.swift.org/mgstanley/32/36508_2.png) [@mgstanley](https://forums.swift.org/u/mgstanley)\
**Post date:** [August 8, 2024, 1:54pm UTC](https://forums.swift.org/t/dears-the-closures-chapter-make-me-drunk/73831/1 "2024-08-08T13:54:47Z")

</div>

That chapter tells Swift’s closure expressions have a clean, clear style, with optimizations that encourage brief, clutter-free syntax in common scenarios.

As programming beginners, I really do not think so.

# [Operator Methods](https://docs.swift.org/swift-book/documentation/the-swift-programming-language/closures/#Operator-Methods)

'''  
let names = ["Chris", "Alex", "Ewa", "Barry", "Daniella"]

let reversedNames = names.sorted(by: \>)

'''

I do not think just "\>" mark can make codes clear to understand.

# [Escaping Closures](https://docs.swift.org/swift-book/documentation/the-swift-programming-language/closures/#Escaping-Closures)

'''  
var completionHandlers: [() -\> Void] =   
func someFunctionWithEscapingClosure(completionHandler: @escaping () -\> Void) {  
completionHandlers.append(completionHandler)  
}

'''  
This grammer is really hard to understand. 😮‍💨

---

<div class="post-metadata">

**Author:** ![stuchlej](https://sea2.discourse-cdn.com/swift/user_avatar/forums.swift.org/stuchlej/32/7751_2.png) [@stuchlej](https://forums.swift.org/u/stuchlej)\
**Post date:** [August 8, 2024, 2:25pm UTC](https://forums.swift.org/t/dears-the-closures-chapter-make-me-drunk/73831/2 "2024-08-08T14:25:06Z")

</div>

I agree with you. From my experience, all of the variants of omissions are very confusing for beginners I have tried to get into Swift (and it was even before [the SE-0279 "controversy"](https://github.com/swiftlang/swift-evolution/blob/main/proposals/0279-multiple-trailing-closures.md)).

I'd say that in the end, the syntax is fine - for somewhat experienced developers. However I think there is certainly a steep learning curve compared to other essential Swift features.

I'd say that you have be patient with this feature in particular.

* * *

Things like _Oprator Methods_ are IMO common syntax among languages (for example `[1, 2, 3].reduce(0, +)` vs. Haskell `foldl(+) 0 [1, 2, 3]`).

If by _escaping closures_ you mean the `@escaping` keyword, you will find such annotations to be common in Swift. However, such annotation are also not unheard of - see for example the Python decorators.