# SE-0335: Introduce existential \`any\`

**URL:** <https://forums.swift.org/t/se-0335-introduce-existential-any/53934>\
**Category:** Proposal Reviews\
**Created:** [December 8, 2021, 9:30pm UTC](https://forums.swift.org/t/se-0335-introduce-existential-any/53934 "2021-12-08T21:30:23Z")\
**Posts on this page:** 1\
**Showing post:** 144

<div class="post-metadata">

**Author:** ![davdroman](https://sea2.discourse-cdn.com/swift/user_avatar/forums.swift.org/davdroman/32/46501_2.png) [@davdroman](https://forums.swift.org/u/davdroman)\
**Post date:** [March 29, 2022, 4:02pm UTC](https://forums.swift.org/t/se-0335-introduce-existential-any/53934/144 "2022-03-29T16:02:25Z")

</div>

> [@ebg](#):
>
> Which compiler flag will enable this warning in Swift 5.6?

There are none (by design):

> [@Finding existentials for \`any\`](https://forums.swift.org/t/finding-existentials-for-any/55956/3):
>
> There isn't currently a way to turn on warnings for missing anys in your code. That's intentional; we're working on a lot of generics ergonomics features right now that may change the way programmers update their current use of existential types. A lot of Swift code today uses existential types where it doesn't need to because existential types were the more natural thing to write. With [opaque parameters](https://github.com/apple/swift-evolution/blob/main/proposals/0341-opaque-parameters.md) and [existential opening for function arguments](https://forums.swift.org/t/pitch-implicitly-opening-existentials/55412) that's being worked on right now, a lot of c…

---

_[View the full topic](https://forums.swift.org/t/se-0335-introduce-existential-any/53934)._