Re: [swift-users] Extensions on Typealiased Existential Protocols

@David But the automatic conformance is currently supported through extension A where Self: B. @Slava When does extension A where Self: B not equal extension B where Self: A? Why would protocol inheritance not be communicative? On June 19, 2017 at 5:26:44 PM, David Sweeris (daveswee...@mac.com)

Re: [swift-users] Extensions on Typealiased Existential Protocols

What I usually do here is: typealias CProtocol = A & B protocol C: CProtocol { } // or just A & B directly, I think extension C {} So it’s a bit silly to me. Jon > On Jun 19, 2017, at 3:44 PM, Slava Pestov via swift-users > wrote: > > Hi Steven, > >> On Jun 19,

[swift-users] Extensions on Typealiased Existential Protocols

Is this error intentional, or a bug? protocol A {} protocol B {} typealias C = A & B // valid extension C {} // Error: Non-nominal type 'C' (aka 'A & B') cannot be extended extension A where Self: B {} // valid struct Foo: C {} // valid Since extension A where Self: B is the same as