# \[Pitch\] Last expression as return value

**URL:** <https://forums.swift.org/t/pitch-last-expression-as-return-value/76958>\
**Category:** Pitches\
**Created:** [January 2, 2025, 12:37am UTC](https://forums.swift.org/t/pitch-last-expression-as-return-value/76958 "2025-01-02T00:37:10Z")\
**Posts on this page:** 1\
**Showing post:** 199

<div class="post-metadata">

**Author:** ![crontab](https://sea2.discourse-cdn.com/swift/user_avatar/forums.swift.org/crontab/32/7374_2.png) [@crontab](https://forums.swift.org/u/crontab)\
**Post date:** [January 7, 2025, 6:03pm UTC](https://forums.swift.org/t/pitch-last-expression-as-return-value/76958/199 "2025-01-07T18:03:42Z")

</div>

Great comment @austintatious, fully agreed.

Besides, if we go a bit higher-level, I think we should acknowledge that keywords not only bear some function in the language, they also serve as visual markers for scanning and understanding the code faster, especially in IDE's, but not only.

There are probably a few other places where Swift's syntax could be simplified by removing a keyword but the price of reducing discoverability by removing an important marker may outweigh the benefits.

Being a staunch minimalist myself as an engineer, I cheered the removal of `return` in single-line function bodies. I cheered the shorter `if let` construct (who didn't?) and many other improvements. But this one crosses a certain line that I can't agree to.

---

_[View the full topic](https://forums.swift.org/t/pitch-last-expression-as-return-value/76958)._