Hello Chris, I think that it would go along the line of thinking that sees static dispatching as an optimisation that should be either enforced by the developer's clear and explicit intent or performed automagically only if the compiler is sure of no side effects occurring.
Sent from my iPhone > On 20 May 2016, at 18:35, Chris Lattner <[email protected]> wrote: > > >> On May 20, 2016, at 9:17 AM, Austin Zheng <[email protected]> wrote: >> >> I almost want to propose forbidding methods in protocol extensions unless >> they're also a requirement in the protocol itself, but I don't think that >> would fly. > > I don’t think that would fly :-). That said, has anyone considered requiring > a keyword on the method in the protocol extension that makes it explicit that > the dispatch is non-dynamic? > > -Chris _______________________________________________ swift-evolution mailing list [email protected] https://lists.swift.org/mailman/listinfo/swift-evolution
