I can not understand why, way in the XXIst century, in a language that from
the beginning supports for unicode identifiers we are at ascii charset
overloading bikeshed. Why type `type` or (in other proposal $, or <> or [] or
whatever<128) if I might press Super-T and get ʧ. Or press Super-G and get ʭ.

I hear that only gurus will write generic code. Might it be, but thousands of
rookies should be able to read this generic code before they make their first
commit.

Gurus will know how to map their keyboards. Rookies on their (win) machines
have circa 1000 glyphs in basic system fonts. (On any linux distro have over
3000).

Why on earth keep on ascii?

IPA: ʅ ʧ ʭ (0x285, 0x2a7, 0x2ad)
Latin-E: « » ¦ 
Latin-A: Ħ ŧ Ŧ Ɏ 
Latin-B: ǁ ǂ 

-- 
Wojciech S. Czarnecki
 << ^oo^ >> OHIR-RIPE

-- 
You received this message because you are subscribed to the Google Groups 
"golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to golang-nuts+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to