How about Syntax.IntegerLiteralDestination as a name?<div><br></div><div>That way just as, for example, CustomStringConvertible can be read to mean “This type can be converted to a string in a custom manner”, we would have Syntax.IntegerLiteralDestination meaning “This type can be the destination for a literal integer in syntax.”</div><div><br></div><div>That said, I think Syntax.IntegerLiteral is sufficient. “This type can be a literal integer in syntax.”</div><div><br></div><div>Nevin<br><br>On Sunday, July 3, 2016, David Sweeris via swift-evolution <<a href="mailto:swift-evolution@swift.org">swift-evolution@swift.org</a>> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
> On Jul 2, 2016, at 23:16, Erica Sadun via swift-evolution <<a href="javascript:;" onclick="_e(event, 'cvml', 'swift-evolution@swift.org')">swift-evolution@swift.org</a>> wrote:<br>
><br>
> Change it to "Syntax.ExpressibleByIntegerLiteral" and I'd be onboard but<br>
> I don't think it would pass the DaveTest despite it being only 2 characters longer.[1]<br>
<br>
Yeah, I agree with "By" instead of "As". It makes it a bit clearer that these protocols kinda work backwards, so to speak. That is, if I understand things correctly, rather than adding functionality/semantics to the conforming type, conforming to a literal protocol adds functionality/semantics to the corresponding literal "type" (which we can't directly interact with because they don't actually exist within Swift's type system).<br>
<br>
- Dave Sweeris<br>
_______________________________________________<br>
swift-evolution mailing list<br>
<a href="javascript:;" onclick="_e(event, 'cvml', 'swift-evolution@swift.org')">swift-evolution@swift.org</a><br>
<a href="https://lists.swift.org/mailman/listinfo/swift-evolution" target="_blank">https://lists.swift.org/mailman/listinfo/swift-evolution</a><br>
</blockquote></div>