Re: [go-nuts] the Dominance of English in Programming Languages

In my view you don't necessarily need to speak English, although it helps a lot. Go uses utf-8 for all identifiers, so assuming you treat the keywords as blobs and just remember when to use which you should be fine. The issue being more that all existing packages worth using are written with Eng

[go-nuts] the Dominance of English in Programming Languages

I recently read an article (German) about the dominance of English in programming languages [1]. It is about the fact that keywords in a language typically are English words. Thus it would be hard for non English speakers to learn programming - argue the authors. I wonder if there is really demand

Re: [go-nuts] Go if else syntax .. suggested replacement

> As language choice becomes more arbitrary, and transpilers more common, > personal preferred syntax / language features may end up being handled like > code formatting rules. So In Peter++ I could then use all the syntax I like, > transpile that to WASM or LLVM, and someone else working on tha

[go-nuts] Re: Go if else syntax .. suggested replacement

imo a very important aspect of a language is enduring syntax stability. Too many 'modern' languages lack even the most fundamental requirement of a solid Language Specification. Well done Go! And love or hate Java, that's what made it stable enough for it's massive and enduring success. Go i

Re: [go-nuts] strange bug

Thanks. Interesting that in all my time with Go I didn’t really think about it. > On Apr 28, 2019, at 10:21 AM, andrey mirtchovski > wrote: > >> But still, it would seem the range index should be unsigned - what would be >> the purpose of it being signed? Similarly, the slice indexing should b

Re: [go-nuts] strange bug

> But still, it would seem the range index should be unsigned - what would be > the purpose of it being signed? Similarly, the slice indexing should be > unsigned as well. Just thinking about it... not the first time this has come up. here are a couple of references: https://groups.google.com/d

Re: [go-nuts] strange bug

But still, it would seem the range index should be unsigned - what would be the purpose of it being signed? Similarly, the slice indexing should be unsigned as well. Just thinking about it... > On Apr 28, 2019, at 10:03 AM, andrey mirtchovski > wrote: > >> So, the question is: why ‘i’ isn’t t

Re: [go-nuts] strange bug

Yes, I heard back from the author that he was using tip. Thanks for the help. > On Apr 28, 2019, at 10:03 AM, andrey mirtchovski > wrote: > >> So, the question is: why ‘i’ isn’t treated as unsigned, since it is a range >> index - won't it always be positive? > > The author of the PR was most

Re: [go-nuts] strange bug

> So, the question is: why ‘i’ isn’t treated as unsigned, since it is a range > index - won't it always be positive? The author of the PR was most likely working on Go's tip (what will become 1.13), where the requirement that the right operator in a shift is an unsigned integer has been lifted.

[go-nuts] strange bug

I accepted a PR for my fixed project. It was done by an expectedly experienced developer and it includes a test case. I find it very hard to believe that the author didn’t run and verify the test case, so that leaves me to believe that something in Go has change

[go-nuts] Need help to launch hello.go

Hi everyone, as you can see from the topic I am new to Go I follow the instruction on this page https://golang.org/doc/code.html#Workspaces to launch hello.go and face some difficulties So, I downloded and installed MSI file foe Windows Here is my Go version: go versi