Re: [swift-evolution] DynamicMemberLookup proposal: status update

Yes indeed! He and I have been exchanging emails :-) -Chris > On Jan 5, 2018, at 5:20 AM, Ben Rimmington wrote: > > Have you seen John Holdsworth's experiments? > > > -- Ben > >> On 4 Jan 2018, at 20:52, Chris Lattner wrote: >> >> Hi everyone, >>

Re: [swift-evolution] DynamicMemberLookup proposal: status update

Have you seen John Holdsworth's experiments? -- Ben > On 4 Jan 2018, at 20:52, Chris Lattner wrote: > > Hi everyone, > > With the holidays and many other things behind us, the core team had a chance > to talk about python interop + the dynamic member

Re: [swift-evolution] DynamicMemberLookup proposal: status update

On Jan 4, 2018, at 3:43 PM, Nevin Brackett-Rozinsky wrote: > > There’s a lot of information here and it’ll take some time to process it all. > My initial reaction is that a “strong type-alias” feature might help. If one > could write (strawman syntax): > > strong typealias Dog = PyVal// A

Re: [swift-evolution] DynamicMemberLookup proposal: status update

There’s a lot of information here and it’ll take some time to process it all. My initial reaction is that a “strong type-alias” feature might help. If one could write (strawman syntax): strong typealias Dog = PyVal// A semantically independent new type extension Dog { // Declarations here

[swift-evolution] DynamicMemberLookup proposal: status update

Hi everyone, With the holidays and many other things behind us, the core team had a chance to talk about python interop + the dynamic member lookup proposal recently. Here’s where things stand: we specifically discussed whether a counter-proposal of using “automatically generated wrappers” or “