# 10 years on, what would you change about Swift?

**URL:** <https://forums.swift.org/t/10-years-on-what-would-you-change-about-swift/71716>\
**Category:** Discussion\
**Created:** [May 9, 2024, 8:38am UTC](https://forums.swift.org/t/10-years-on-what-would-you-change-about-swift/71716 "2024-05-09T08:38:56Z")\
**Posts on this page:** 1\
**Showing post:** 118

<div class="post-metadata">

**Author:** ![vns](https://sea2.discourse-cdn.com/swift/user_avatar/forums.swift.org/vns/32/37396_2.png) [@vns](https://forums.swift.org/u/vns)\
**Post date:** [May 14, 2024, 7:50am UTC](https://forums.swift.org/t/10-years-on-what-would-you-change-about-swift/71716/118 "2024-05-14T07:50:19Z")

</div>

> [@dmk](#):
>
> To migrate to Swift 6, I would need to rewrite this piece of code somehow. Either add `any` everywhere I mention `Service1`, `Service2`, `Service3`,

This won’t be required in Swift 6 by default. But that’s not main question, since `Service` and `any Service` here is the same thing, just second one is explicit. And if there are any performance implications you are concerned using existential, it is fine to use `any` (especially if alternatives are unavailable or fit less). It is good to prefer generic/`some` (since generics itself has a viral tendency) if possible, but still if that is not a critical part, you it won’t have performance implications.

---

_[View the full topic](https://forums.swift.org/t/10-years-on-what-would-you-change-about-swift/71716)._