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

ready addressed, > but will the default behavior (i.e. that of something that doesn’t conform to > CustomPlaygroundRepresentable) remain the same? > > Saagar Jha > >> On Jan 9, 2018, at 15:19, Connor Wakamo via swift-evolution >> <swift-evolution@swift.org <mailt

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

> On Jan 9, 2018, at 4:21 PM, Ben Rimmington wrote: > > Something like this was attempted (and reverted) for Swift 3: > > > >

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

Good afternoon, In preparation for ABI stability, I’ve reviewed the API exposed by the standard library for providing customized “quick looks” in playgrounds. This is exposed as the PlaygroundQuickLook enum and the CustomPlaygroundQuickLookable protocol. The PlaygroundQuickLook has a handful

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

> On Jan 9, 2018, at 10:02 PM, Chris Lattner <clatt...@nondot.org> wrote: > > On Jan 9, 2018, at 3:19 PM, Connor Wakamo via swift-evolution > <swift-evolution@swift.org <mailto:swift-evolution@swift.org>> wrote: >> Good afternoon, > > Hi Connor, &g

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

> On Jan 10, 2018, at 1:58 AM, Ian Partridge <i...@poncho.org.uk> wrote: > > On 9 January 2018 at 23:19, Connor Wakamo via swift-evolution > <swift-evolution@swift.org> wrote: >> To that end, I am proposing the following: >> >> - Introduce a n

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

> On Jan 10, 2018, at 12:39 PM, Saagar Jha wrote: > > Well, in my experience performance issues tend to come not from trying to > display a single object, but when you have an aggregation of many objects. > For example, displaying one Int is pretty lightweight, as is an

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

> On Jan 10, 2018, at 2:34 PM, Saagar Jha wrote: > > > Saagar Jha > >> On Jan 10, 2018, at 14:10, Connor Wakamo > > wrote: >> >>> On Jan 10, 2018, at 12:39 PM, Saagar Jha >>

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

> On Jan 12, 2018, at 11:02 PM, Chris Lattner wrote: > >> On Jan 12, 2018, at 6:22 PM, Connor Wakamo > > wrote: >> The second case, and the one I’m more worried about, is subclassing. If, for instance, you have the

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

> On Jan 13, 2018, at 8:20 AM, Karl Wagner <razie...@gmail.com> wrote: > > > >> On 13. Jan 2018, at 03:22, Connor Wakamo via swift-evolution >> <swift-evolution@swift.org <mailto:swift-evolution@swift.org>> wrote: >> >> >

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

> On Jan 13, 2018, at 2:18 PM, Erica Sadun <er...@ericasadun.com> wrote: > > On Jan 11, 2018, at 1:40 PM, Jonathan Hull via swift-evolution > <swift-evolution@swift.org <mailto:swift-evolution@swift.org>> wrote: >> >> >>> On Jan 11, 2

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

> On Jan 11, 2018, at 11:51 PM, Chris Lattner wrote: > > On Jan 11, 2018, at 11:22 AM, Connor Wakamo > wrote: I don’t think we can change this to return `Any` instead of `Any?`. I think there are potentially cases

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

> On Jan 10, 2018, at 4:21 PM, Chris Lattner wrote: > >> On Jan 10, 2018, at 2:10 PM, Connor Wakamo > > wrote: >>> What is the use-case for a type conforming to this protocol but returning >>> nil? If there is a use case for