# Forced non optional coalesce that behaves like a guard else nothing statement

**URL:** <https://forums.swift.org/t/forced-non-optional-coalesce-that-behaves-like-a-guard-else-nothing-statement/34723>\
**Category:** Pitches\
**Created:** [March 23, 2020, 1:52pm UTC](https://forums.swift.org/t/forced-non-optional-coalesce-that-behaves-like-a-guard-else-nothing-statement/34723 "2020-03-23T13:52:44Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![mattpolzin](https://sea2.discourse-cdn.com/swift/user_avatar/forums.swift.org/mattpolzin/32/6041_2.png) [@mattpolzin](https://forums.swift.org/u/mattpolzin)\
**Post date:** [March 23, 2020, 2:30pm UTC](https://forums.swift.org/t/forced-non-optional-coalesce-that-behaves-like-a-guard-else-nothing-statement/34723/5 "2020-03-23T14:30:02Z")

</div>

On the other hand, see future directions at the end of the original post of this thread: [Uninhabited Type (Never) Conversions](https://forums.swift.org/t/uninhabited-type-never-conversions/34669)

[EDIT] Note that the above linked thread is not an accepted direction for the language, it’s just a discussion.

Not sure I would want to be able to avoid guard statements where I’d otherwise be returning or continuing but the idea of throwing if nil coalescing fails is appealing to me.

---

_[View the full topic](https://forums.swift.org/t/forced-non-optional-coalesce-that-behaves-like-a-guard-else-nothing-statement/34723)._