# Swift 5.6 released!

**URL:** <https://forums.swift.org/t/swift-5-6-released/55931>\
**Category:** Announcements\
**Created:** [March 14, 2022, 6:49pm UTC](https://forums.swift.org/t/swift-5-6-released/55931 "2022-03-14T18:49:19Z")\
**Posts on this page:** 1\
**Showing post:** 22

<div class="post-metadata">

**Author:** ![hborla](https://sea2.discourse-cdn.com/swift/user_avatar/forums.swift.org/hborla/32/27563_2.png) [@hborla](https://forums.swift.org/u/hborla)\
**Post date:** [March 21, 2022, 10:17pm UTC](https://forums.swift.org/t/swift-5-6-released/55931/22 "2022-03-21T22:17:10Z")

</div>

> [@AlexanderM](#):
>
> Is there any flag for turning on "Swift 6 mode", i.e., making them required even in Swift 5.6?

Not yet:

> [@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/swift-5-6-released/55931)._