1. 14
  1. 6

    I’m currently working at a place where code is written in one of the local languages, and now I’m curious how Go works with writing systems that don’t have letter case.

    1. 3

      According to the spec, the first letter of your identifier must be in the ‘Lu’ letter case. So you’d have to write

      var X日本語 string = "nihongo"
      

      to export it. There’s a proposal to allow a way to export uncased identifiers, but it hasn’t gotten anyplace concrete.

      1. 9

        I’m kind of appalled at, somewhat unsurprised regarding, but, most importantly, incredibly amused about the fact that one of Go’s fundamental design decisions has exceeded its being merely technically provincial to become literally provincial besides.

        1. 14

          I have no idea what you just wrote, even though I understood all the words.

          1. 6

            I’ll give it a try, too, just because language is fun: “I was not surprised by a design decision in Go, even though I felt horror and laughed. It began as ‘provincial’ in the sense of being naïve, and ended up ‘provincial’ in the sense of working only in a single culture.”

            1. 4

              “A Go design decision that’s seems purely technical ends up being English-centric due to implementation.”

              1. 3

                It honestly looks like a GPT-generated text.

                1. 1

                  I think this is called “purple prose” (https://en.wikipedia.org/wiki/Purple_prose).

          2. 1

            I’d never heard of this feature, but I agree that capitalization feels like the wrong way. It makes me appreciate the javascript # which also felt “ugly” but does have the same effect of not requiring you to carry around memorized context.