[WTF] Go Unicode Hack to Get Pseudo-Generics

Re:[WTF] Go Unicode Hack to Get Pseudo-Generics by tyingq on Friday May 05, 2017 @06:57PM (#14277428)

No, it's scary. I liked the comment because it highlights that this isn't just a golang problem. Nor is it just a code problem, lots of recent stories of browsers not knowing quite when to show unicode chars or punycode in the omnibox, for example.

Not sure that disallowing it everywhere is the answer either. As an American that speaks only English, I'm probably not the best person to answer what is the right approach.

[ Parent | on HN ]

Re:[WTF] Go Unicode Hack to Get Pseudo-Generics by Jimmie_Rustle on Friday May 05, 2017 @07:02PM (#14277460)

| As an American that speaks only English, I'm probably not the best person to answer what is the right approach.

Why not, most code is written in English.

[ Parent | on HN ]

Re:[WTF] Go Unicode Hack to Get Pseudo-Generics by saurik on Saturday May 06, 2017 @03:22AM (#14279145)

Because if you speak only English and are surrounded by vast stretches of land on every side of you where people mostly only speak English, you don't feel the pain. (And seriously? One reason most code might be written only in English is due to the systemic bias of programming environments that only support English.)

[ Parent | on HN ]

Re:[WTF] Go Unicode Hack to Get Pseudo-Generics by tyingq on Friday May 05, 2017 @07:07PM (#14277491)

I have seen a fair amount of non ASCII string literals. Multiple currencies, for example.

I assume utf8 has some problematic glyphs in this space.

[ Parent | on HN ]

Re:[WTF] Go Unicode Hack to Get Pseudo-Generics by zzzcpan on Friday May 05, 2017 @07:03PM (#14277466)

English is my third language, so I guess my perspective on this problem does matter a bit.

[ Parent | on HN ]