What is your use case for this? On Mon, Oct 2, 2017 at 10:56 David Sweeris via swift-evolution < swift-evolution@swift.org> wrote:
> > On Oct 1, 2017, at 22:01, Chris Lattner via swift-evolution < > swift-evolution@swift.org> wrote: > > > On Oct 1, 2017, at 9:26 PM, Kenny Leung via swift-evolution < > swift-evolution@swift.org> wrote: > > Hi All. > > I’d like to help as well. I have fun with operators. > > There is also the issue of code security with invisible unicode characters > and characters that look exactly alike. > > > Unless there is a compelling reason to add them, I think we should ban > invisible characters. What is the harm of characters that look alike? > > > Especially if people want to use the character in question as both an > identifier and an operator: We can make the character an identifier and its > lookalike an operator (or the other way around). > > - Dave Sweeris > _______________________________________________ > swift-evolution mailing list > swift-evolution@swift.org > https://lists.swift.org/mailman/listinfo/swift-evolution >
_______________________________________________ swift-evolution mailing list swift-evolution@swift.org https://lists.swift.org/mailman/listinfo/swift-evolution
