> That’s the other part of my argument: if it is true that Swift code only > needs to conform to ObjC protocols with optional requirements, but Swift code > does not need to invoke optional requirements of ObjC protocols except very > rarely, then it’s okay for calling-an-optional-requirement not to be part of > the Swift language.
How much of a complication is the `methodName?` behavior? If you're confident that `optional` is the wrong choice for protocols designed in the future, perhaps you could just make it impossible to declare a new optional requirement in Swift, but leave the calling behavior as-is? -- Brent Royal-Gordon Architechies _______________________________________________ swift-evolution mailing list [email protected] https://lists.swift.org/mailman/listinfo/swift-evolution
