[swift-evolution] Proposal: Introduce User-defined "Dynamic Member Lookup" Types

Chris Lattner clattner at nondot.org
Wed Dec 6 23:41:11 CST 2017


On Dec 6, 2017, at 8:11 PM, Joe DeCapo via swift-evolution <swift-evolution at swift.org> wrote:
>> Has all of this ruined the language thus far? No. Because the Swift core team doesn’t design, and the Swift community doesn’t adopt, ill-designed APIs that turn these facts into problems.
> 
> 
> Yeah, I think I'd prefer this to stay as a normal protocol conformance. But if the proportion of resistance is high enough,…

Until, and if, the “resistance” presents some conceptual explanation of how this could cause harm (I’m not asking for anything concrete, just a logical series of events that causes a plausible problem in practice), my belief is that the Swift community will see this as unwarranted fear.

This is particularly true given that the proposal is completely consistent with previous design decisions in Swift, decisions which have served us well.

-Chris



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.swift.org/pipermail/swift-evolution/attachments/20171206/3917a60f/attachment.html>


More information about the swift-evolution mailing list