On 6/6/2018 2:25 PM, Hans Åberg via
Unicode wrote:
On 4 Jun 2018, at 21:49, Manish Goregaokar via Unicode <unicode@unicode.org> wrote:The Rust community is considering adding non-ascii identifiers, which follow UAX #31 (XID_Start XID_Continue*, with tweaks). The proposal also asks for identifiers to be treated as equivalent under NFKC.So, in this language, if one defines a projection function 𝜋 and the usual constant π, what is 𝜋(π) supposed to mean? - Just curious. In a language where one writes ASCII "pi" instead, what is pi(pi) supposed to mean? A./ |
- Re: Can NFKC turn valid UAX 31 identif... Richard Wordingham via Unicode
- Re: Can NFKC turn valid UAX 31 ide... Mark Davis ☕️ via Unicode
- Re: Can NFKC turn valid UAX 31 identifiers ... Rebecca T via Unicode
- Re: Can NFKC turn valid UAX 31 identif... Martin J. Dürst via Unicode
- Re: Can NFKC turn valid UAX 31 ide... Alastair Houghton via Unicode
- Re: Can NFKC turn valid UAX 31... Philippe Verdy via Unicode
- Re: Can NFKC turn valid UAX 31 identifiers ... Alastair Houghton via Unicode
- Re: Can NFKC turn valid UAX 31 identif... Alastair Houghton via Unicode
- Re: Can NFKC turn valid UAX 31 identifiers ... Henri Sivonen via Unicode
- Re: Can NFKC turn valid UAX 31 identifiers ... Hans Åberg via Unicode
- Re: Can NFKC turn valid UAX 31 identif... Asmus Freytag via Unicode
- Re: Can NFKC turn valid UAX 31 ide... Hans Åberg via Unicode
- Re: Can NFKC turn valid UAX 31 identif... Philippe Verdy via Unicode
- Re: Can NFKC turn valid UAX 31 ide... Hans Åberg via Unicode
- Re: Can NFKC turn valid UAX 31 identifiers ... Richard Wordingham via Unicode
- Re: Can NFKC turn valid UAX 31 identifiers ... Joan Montané via Unicode
- Re: Can NFKC turn valid UAX 31 identif... Philippe Verdy via Unicode
- Re: Can NFKC turn valid UAX 31 identif... Richard Wordingham via Unicode