on Sun Sep 18 2016, Xiaodi Wu <swift-evolution@swift.org> wrote:

>   2d) Confusables: I think the last time we had this discussion, it was
> apparent that it'd be difficult to decide which confusables to allow or
> disallow after some of the low-hanging fruit is taken care of by Unicode
> normalization (see item 2a); the Unicode Consortium-provided list seems too
> quick to call two things "confusable" for our purposes (with criteria that
> might be relevant for URLs or other use cases, but casting too wide a net
> perhaps for Swift identifiers)

Confusables can IMO be entirely handled with warnings, which requires
much less discussion here than if it were a language feature.

-- 
-Dave

_______________________________________________
swift-evolution mailing list
swift-evolution@swift.org
https://lists.swift.org/mailman/listinfo/swift-evolution

Reply via email to