# Introducing Namespacing for Common Swift Error Scenarios

**URL:** <https://forums.swift.org/t/introducing-namespacing-for-common-swift-error-scenarios/10773>\
**Category:** Pitches\
**Created:** [March 9, 2018, 8:34pm UTC](https://forums.swift.org/t/introducing-namespacing-for-common-swift-error-scenarios/10773 "2018-03-09T20:34:39Z")\
**Posts on this page:** 1\
**Showing post:** 22

<div class="post-metadata">

**Author:** ![davedelong](https://sea2.discourse-cdn.com/swift/user_avatar/forums.swift.org/davedelong/32/38708_2.png) [@davedelong](https://forums.swift.org/u/davedelong)\
**Post date:** [June 14, 2018, 11:42pm UTC](https://forums.swift.org/t/introducing-namespacing-for-common-swift-error-scenarios/10773/22 "2018-06-14T23:42:39Z")

</div>

We've finally gotten around to putting together a proposal for this, which can be seen here (PR): [[Proposal] Introducing Namespacing for Common Swift Error Scenarios by erica · Pull Request #861 · apple/swift-evolution · GitHub](https://github.com/apple/swift-evolution/pull/861)

The main difference is that we no longer have a top-level `Fatal` type, but instead have added an overload of `fatalError()` that allows you to pass in some pre-defined reasons.

---

_[View the full topic](https://forums.swift.org/t/introducing-namespacing-for-common-swift-error-scenarios/10773)._