# Pre-pitch: remove the implicit initialization of Optional variables

**URL:** <https://forums.swift.org/t/pre-pitch-remove-the-implicit-initialization-of-optional-variables/52300>\
**Category:** Pitches\
**Created:** [September 22, 2021, 10:02pm UTC](https://forums.swift.org/t/pre-pitch-remove-the-implicit-initialization-of-optional-variables/52300 "2021-09-22T22:02:21Z")\
**Posts on this page:** 1\
**Showing post:** 28

<div class="post-metadata">

**Author:** ![tera](https://sea2.discourse-cdn.com/swift/user_avatar/forums.swift.org/tera/32/38201_2.png) [@tera](https://forums.swift.org/u/tera)\
**Post date:** [September 24, 2021, 1:56am UTC](https://forums.swift.org/t/pre-pitch-remove-the-implicit-initialization-of-optional-variables/52300/28 "2021-09-24T01:56:41Z")

</div>

listing the previous attempts:

nov 2017 [Pitch: Remove default initialization of optional bindings](https://forums.swift.org/t/pitch-remove-default-initialization-of-optional-bindings/6961)  
jan 2019 [Remove implicit initialization of Optionals?](https://forums.swift.org/t/remove-implicit-initialization-of-optionals/19482)  
jun 2019 [PrePitch: Optional variables should require explicit initialization](https://forums.swift.org/t/prepitch-optional-variables-should-require-explicit-initialization/26077)

the other radical way of solving this inconsistency is to introduce some DefaultValueInitializable (?) protocol. Optionals would confirm to it, so could user types.

---

_[View the full topic](https://forums.swift.org/t/pre-pitch-remove-the-implicit-initialization-of-optional-variables/52300)._