<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div class="">[Proposal: <a href="https://github.com/apple/swift-evolution/blob/master/proposals/0115-literal-syntax-protocols.md" class="">https://github.com/apple/swift-evolution/blob/master/proposals/0115-literal-syntax-protocols.md</a> ]</div><br class=""><div><blockquote type="cite" class=""><div class="">On Jul 3, 2016, at 9:52, David Sweeris via swift-evolution <<a href="mailto:swift-evolution@swift.org" class="">swift-evolution@swift.org</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div class=""><br class=""><blockquote type="cite" class="">On Jul 2, 2016, at 23:16, Erica Sadun via swift-evolution <<a href="mailto:swift-evolution@swift.org" class="">swift-evolution@swift.org</a>> wrote:<br class=""><br class="">Change it to "Syntax.ExpressibleByIntegerLiteral" and I'd be onboard but<br class="">I don't think it would pass the DaveTest despite it being only 2 characters longer.[1]<br class=""></blockquote><br class="">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).</div></div></blockquote><br class=""></div><div>I like "By" <i class="">much</i> better than "As". For me, "expressible as integer literal" has the meaning we <i class="">don't</i> want, with no hint of ambiguity: "you can go from a concrete type to a literal" (rather than the correct "you can go from a literal to a concrete type").</div><div><br class=""></div><div>Jordan</div><br class=""></body></html>