# Rename fatalError()

**URL:** <https://forums.swift.org/t/rename-fatalerror/14310>\
**Category:** Pitches\
**Created:** [July 7, 2018, 7:07pm UTC](https://forums.swift.org/t/rename-fatalerror/14310 "2018-07-07T19:07:11Z")\
**Posts on this page:** 1\
**Showing post:** 9

<div class="post-metadata">

**Author:** ![Erica\_Sadun](https://sea2.discourse-cdn.com/swift/user_avatar/forums.swift.org/erica_sadun/32/243_2.png) [@Erica\_Sadun](https://forums.swift.org/u/Erica_Sadun)\
**Post date:** [July 9, 2018, 3:11pm UTC](https://forums.swift.org/t/rename-fatalerror/14310/9 "2018-07-09T15:11:06Z")

</div>

The suggestions in this thread seem to want to rename `fatalError` rather than redesign it. I'd like to point out links that look at fatal outcomes through redesign:

- [Introducing Namespacing for Common Swift Error Scenarios - #31 by davedelong](https://forums.swift.org/t/introducing-namespacing-for-common-swift-error-scenarios/10773/31)
- [[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)

I think `fatalError` is a term of art, although I agree `die` is to the point.

---

_[View the full topic](https://forums.swift.org/t/rename-fatalerror/14310)._