Re: [swift-evolution] [Pitch #2] Introduce user-defined dynamically "callable" types

DynamicCallable.md DynamicMemberLookup.md JavaScriptCore.JSValue If the JSValue class

Re: [swift-evolution] [Pitch #2] Introduce user-defined dynamically "callable" types

> On 22 Nov 2017, at 09:10, Alex Hoppen via swift-evolution > wrote: > > Would we really need the dynamicCall(method:arguments:) method and > DynamicCallableKeywordedMethod protocol for Smalltalk-like languages? > > I think in these languages, we could achieve

Re: [swift-evolution] [Pitch #2] Introduce user-defined dynamically "callable" types

Would we really need the dynamicCall(method:arguments:) method and DynamicCallableKeywordedMethod protocol for Smalltalk-like languages? I think in these languages, we could achieve keyword-argument-sensitive method dispatch purely based on DynamicMemberLookupProtocol and

Re: [swift-evolution] [Pitch #2] Introduce user-defined dynamically "callable" types

I have several questions/issues in this new iteration: • Why does DynamicCallableWithKeywordsToo inherit from DynamicCallable? For an interop layer for Python-style languages, we would be interested in providing conformance to DynamicCallableWithKeywordsToo (like you did in your example), but

Re: [swift-evolution] [Pitch #2] Introduce user-defined dynamically "callable" types

> On Nov 20, 2017, at 10:07 PM, Chris Lattner via swift-evolution > wrote: > > Hi All, > > I’ve significantly revised the ‘dynamic callable’ pitch, here’s a second > edition: Ugh, the actual correct link is:

[swift-evolution] [Pitch #2] Introduce user-defined dynamically "callable" types

Hi All, I’ve significantly revised the ‘dynamic callable’ pitch, here’s a second edition: https://gist.github.com/lattner/b016e1cf86c43732c8d82f90e5ae5438 I’ve incorporated a bunch of feedback from the first round of discussion: - I’ve significantly increased the motivation section, talking