Maybe just a warning + fix-it would be sufficient? On Mon, Jul 11, 2016 at 19:02 Jacob Bandes-Storch via swift-evolution < [email protected]> wrote:
> Tangential: Is there any way to make it impossible to call these > literal-initializers explicitly, instead requiring "<literal> as T" or just > "<literal>" in a typed context? > > I have seen several explicit calls of these initializers where literals > would have been more appropriate, such as "Set(arrayLiteral: foo, bar)", > and I think this only happens because folks find these initializers via > code completion. I can't think of any reason why you'd want to invoke one > by name rather than by using a literal. > > Jacob > > On Mon, Jul 11, 2016 at 4:16 PM, Chris Lattner via swift-evolution < > [email protected]> wrote: > >> Proposal Link: >> https://github.com/apple/swift-evolution/blob/master/proposals/0115-literal-syntax-protocols.md >> >> The review of "SE-0115: Rename Literal Syntax Protocols " ran from Active >> review July 1...7. The proposal has been *accepted*: >> >> The community and core team agree that this proposal is a better set of >> names for these protocols. The core team agrees with the community >> sentiment that “By” is better than “As” in the protocol names, and has >> accepted the proposal with this revision. >> >> Thank you to Matthew Johnson and many others for driving this discussion >> forward! >> >> -Chris Lattner >> Review Manager >> >> >> _______________________________________________ >> swift-evolution mailing list >> [email protected] >> https://lists.swift.org/mailman/listinfo/swift-evolution >> > > _______________________________________________ > swift-evolution mailing list > [email protected] > https://lists.swift.org/mailman/listinfo/swift-evolution >
_______________________________________________ swift-evolution mailing list [email protected] https://lists.swift.org/mailman/listinfo/swift-evolution
