> On Nov 10, 2017, at 12:04 PM, Joe Groff via swift-evolution > <[email protected]> wrote: > > I don't like the idea of some calls having wildly different semantics from > others; it's difficult enough to tell what exactly a call might be doing > already. Since we also lack the more obvious static "Callable" protocol idea > to give even well-typed call syntax to user-defined types, this also seems > like it'd be easily abused for that purpose too.
We already have that though, with the Objective-C bridge. How is the proposed behavior here more wildly different than the semantics of non-@objc, @objc, and @objc dynamic calls? Charles _______________________________________________ swift-evolution mailing list [email protected] https://lists.swift.org/mailman/listinfo/swift-evolution
