[swift-evolution] Allowing Characters for use as Custom Operators

Dennis Lysenko dennis.s.lysenko at gmail.com
Sat Jan 9 21:50:49 CST 2016

Chris, perhaps there is a disconnect in our perceptions of the commonly
proposed list. Based on the way you and others have referenced the commonly
proposed list, it comes off as a blacklist of sorts. That is, "it's on the
commonly proposed list" seems to be seen as an argument against a proposal.
I only worry that the mere presence of something on the commonly proposed
list will serve as a deterrent to legitimate proposals involving it in the

If you have taken that into consideration when deciding to place infix
functions on the commonly proposed list then fair enough. I just feel that
infix functions have not been discussed nearly as much as, say,
"indentation over brace syntax" or "getting rid of ternary", and it's a bit
preemptive to put such a dent in potential future discussion because you
personally cannot imagine a use case warranting the language change.

Out of curiosity, has there even been a top-level proposal for infix
functions that generated significant discussion?

On Sat, Jan 9, 2016 at 5:23 PM Chris Lattner <clattner at apple.com> wrote:

> On Jan 9, 2016, at 11:56 AM, Dennis Lysenko <dennis.s.lysenko at gmail.com>
> wrote:
> Chris, hmm... Can you really say that this is the only problem that would
> warrant infix functions? To say what you just seemingly implies that you
> believe the use cases outlined here are the only reason one would want
> infix operators, and that the use cases outlined here don't warrant infix
> functions.
> I'm sure there are plenty more reasons for implementing infix functions
> and I think it would be reactionary to effectively discourage their
> consideration on the basis of one tangentially related email chain.
> I’m saying that I cannot personally imagine a use-case compelling enough
> to make the language more complicated for (including the ones listed on the
> thread).  If you can, please share them and we can discuss it.
> -Chris
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.swift.org/pipermail/swift-evolution/attachments/20160110/5828e8b6/attachment.html>

More information about the swift-evolution mailing list