Re:How Go improves expressiveness without sacrificing perfor...
by stonemetal on Saturday February 11, 2012 @10:11PM
(#3580987)
There is a reason why it is Go and not the Google C Compiler(They could call it GCC so we don't even have to learn a new compiler name it would be great day for not changing anything). If it were identical to C what would be the point really?
Incidentally a := 5 is a short hand for the Cish int a = 5; = is still general assignment. The extra colon causes a variable declaration with type inference.
If you don't know Go and you look at this 'make([]E, 1000)'. What does it tell you? How about this 'make(map[string]int) or make(chan int) ?'
I don't know Go 'make([]E, 1000)' My take is it is making something maybe even 1000 of them. make(map[string]int) It is making a hashmap with strings and ints, probably with strings being the key and ints being the value. make(chan int) It is making a chan int whatever in the heck that is.
Incidentally a := 5 is a short hand for the Cish int a = 5; = is still general assignment. The extra colon causes a variable declaration with type inference.
If you don't know Go and you look at this 'make([]E, 1000)'. What does it tell you? How about this 'make(map[string]int) or make(chan int) ?'
I don't know Go 'make([]E, 1000)' My take is it is making something maybe even 1000 of them. make(map[string]int) It is making a hashmap with strings and ints, probably with strings being the key and ints being the value. make(chan int) It is making a chan int whatever in the heck that is.