I understand the technical problem here, and killed my hope for "nominal" operators long time ago with fire.
But if someone here uses Kotlin, they know very well how great it is to be able to infix functions of 2 parameters like they were operators: it makes code extremely clean and readable, and it's extremely useful when writing DSLs. Elviro > Il giorno 01 ago 2017, alle ore 03:29, Chris Lattner via swift-evolution > <[email protected]> ha scritto: > > >> On Jul 31, 2017, at 2:09 PM, Gor Gyolchanyan via swift-evolution >> <[email protected] <mailto:[email protected]>> wrote: >> >> So I was thinking the other day (and by "the other day" I mean "It just >> occurred to me") that Swift's custom operator declaration mechanism is >> pretty sweet (it's become even sweeter ever since numeric precedence values >> were replaced with purely relativistic precedence trees). There are >> currently only two problems with them that grind my operator-declaring >> endeavors to a painful halt: >> 1. The fact that most punctuation characters on the keyboard (think - >> ASCII) are reserved, so any custom operator either has to be a long sequence >> of two or three non-reserved ASCII characters or have to include >> difficult-to-type unicode punctuation characters. >> 2. The fact that anything that passes as an identifier character (which >> includes a surprisingly wide array of punctuation characters) is off the >> table as well. > > See the 3rd entry of: > https://github.com/apple/swift-evolution/blob/master/commonly_proposed.md > <https://github.com/apple/swift-evolution/blob/master/commonly_proposed.md> > > -Chris > > > _______________________________________________ > 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
