Re: [swift-evolution] Protocol conformance error

If we have: class N: A {} you can pass an N into C’s test(x:), since N is an A, but not M’s test(x:), since N is not a B. Thus, it’s not a valid conformance. Saagar Jha > On Jan 17, 2018, at 00:04, Roshan via swift-evolution > wrote: > > Hi, > > Cross posting

Re: [swift-evolution] [Pitch] Percentage Type

Saagar Jha > On Jan 17, 2018, at 16:56, Xiaodi Wu via swift-evolution > wrote: > > On Wed, Jan 17, 2018 at 2:04 AM, David Sweeris > wrote: > > > Sent from my iPhone > > > On Jan 16, 2018, at 23:45, Jonathan Hull

Re: [swift-evolution] No disjunctions in type constraints: why?

The “Swifty” way of doing such a thing is to have the types you care about conform to a protocol that clearly defines the API you’re trying to expose. For example: protocol Fooable { func doFoo() } extension Int: Fooable { func doFoo() { print("I’m an Int")

Re: [swift-evolution] [Proposal] Revamp the playground quicklook APIs

Saagar Jha > On Jan 9, 2018, at 22:02, Chris Lattner via swift-evolution > wrote: > > On Jan 9, 2018, at 3:19 PM, Connor Wakamo via swift-evolution > > wrote: >> Good afternoon, > > Hi Connor, > > Huge

Re: [swift-evolution] [Proposal] Revamp the playground quicklook APIs

CustomPlaygroundRepresentationConvertible? Saagar Jha > On Jan 11, 2018, at 11:22, Connor Wakamo via swift-evolution > wrote: > > > >> On Jan 10, 2018, at 4:21 PM, Chris Lattner > > wrote: >> >>> On Jan 10, 2018,

<    1   2