# SE-0309: Unlock existential types for all protocols

**URL:** <https://forums.swift.org/t/se-0309-unlock-existential-types-for-all-protocols/47515>\
**Category:** Proposal Reviews\
**Created:** [April 17, 2021, 7:56pm UTC](https://forums.swift.org/t/se-0309-unlock-existential-types-for-all-protocols/47515 "2021-04-17T19:56:29Z")\
**Posts on this page:** 1\
**Showing post:** 118

<div class="post-metadata">

**Author:** ![Avi](https://sea2.discourse-cdn.com/swift/user_avatar/forums.swift.org/avi/32/2962_2.png) [@Avi](https://forums.swift.org/u/Avi)\
**Post date:** [May 2, 2021, 2:16pm UTC](https://forums.swift.org/t/se-0309-unlock-existential-types-for-all-protocols/47515/118 "2021-05-02T14:16:29Z")

</div>

> [@sighoya](#):
>
> In Swift a protocol type, whatever this means. Generally, a type which steal literals/values from other types, usually base types like integer, structs ... .

By that definition, `some P` isn't existential. `some P` is shorthand, with the added benefit of hiding the real type from the caller. But that's all a compiler trick. `some P` is a stand-in from the perspective of the _developer_, never the compiler.

`some P` behaves like the following:

```swift
// magic modifier to hide the real type from everyone else.
private(type) typealias HiddenP = Int

public func f() -> HiddenP {}

```

One would not consider `HiddenP` to be an existential, and `some P` is nothing more than Swift's actual implementation of my made-up `typealias` modifier.

---

_[View the full topic](https://forums.swift.org/t/se-0309-unlock-existential-types-for-all-protocols/47515)._
