<div style="white-space:pre-wrap">I like how your suggestion reads. It will namespace all literal convertibles while also reading more clearly on what conforming to the protocol implies. I now understand the intent of the Syntax namespace however I think you suggested naming would be better. <br><br>-Shawn</div><br><div class="gmail_quote"><div dir="ltr">On Wed, Jun 22, 2016 at 11:26 PM David Sweeris via swift-evolution <<a href="mailto:swift-evolution@swift.org">swift-evolution@swift.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
> On Jun 22, 2016, at 19:35, Dmitri Gribenko <<a href="mailto:gribozavr@gmail.com" target="_blank">gribozavr@gmail.com</a>> wrote:<br>
><br>
>> On Wed, Jun 22, 2016 at 5:15 PM, David Sweeris <<a href="mailto:davesweeris@mac.com" target="_blank">davesweeris@mac.com</a>> wrote:<br>
>> That's a really interesting idea. Is "Syntax" a placeholder, or is that the intended name?<br>
><br>
> It is the best name we could come up with, we are open to better suggestions.<br>
<br>
I guess it depends on the intended semantics of the "namespace". If the purpose is to be a container for the various LiteralConvertible protocols, then maybe something like `AcceptsLiteralType.Integer` might be better? It's a bit wordy, though.<br>
<br>
<br>
>> Also, why an enum? Especially one without any cases...<br>
><br>
> It is not possible to create an instance of an enum that does not have<br>
> cases. It becomes essentially a namespace.<br>
<br>
Oh that's a clever work-around. I like it :-)<br>
<br>
- Dave Sweeris<br>
_______________________________________________<br>
swift-evolution mailing list<br>
<a href="mailto:swift-evolution@swift.org" target="_blank">swift-evolution@swift.org</a><br>
<a href="https://lists.swift.org/mailman/listinfo/swift-evolution" rel="noreferrer" target="_blank">https://lists.swift.org/mailman/listinfo/swift-evolution</a><br>
</blockquote></div>