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

2019-04-28 Thread Chris Burkert
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

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

2019-04-28 Thread Mike Schinkel
> 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

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

2019-04-28 Thread whitehexagon via golang-nuts
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

Re: [go-nuts] strange bug

2019-04-28 Thread robert engels
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

Re: [go-nuts] strange bug

2019-04-28 Thread andrey mirtchovski
> 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:

Re: [go-nuts] strange bug

2019-04-28 Thread robert engels
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

Re: [go-nuts] strange bug

2019-04-28 Thread robert engels
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

2019-04-28 Thread andrey mirtchovski
> 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

2019-04-28 Thread robert engels
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

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

2019-04-28 Thread Avetis Sargsian
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