> I edited that part of the comment out because it was not really related to anything, but I meant that all identifiers go into a single namespace, e.g if you have a package called bytes you can't call a variable bytes, if you have a struct type called bytes, you can't call the instance bytes
package main
import (
"container/list"
"fmt"
)
func main() {
list := list.New()
list.PushBack(10)
list2 := list.New()
list2.PushBack(10)
fmt.Println(list)
fmt.Println(list2)
}
If I decided to re-use the package name more than once it'd be `list1, list2`
I guess it's probably a programming culture thing, but I wouldn't use the word `list` to begin with. I'd use `l1`, `l2` etc. in the case where the name isn't important. It conveys no less information than `list` and short variable names AFAIK are already idiomatic so it's not even unconventional... But with all that said, `list2` wasn't a very good variable name to begin with. If you needed more than one list, then they clearly served different purposes and in that case it makes sense to name them as such: `apples`, `oranges`, `input`, `output`.
import (
cont_list "container/list"
)
func main() {
list := cont_list.New()
}Hint: wait a few minutes, it's the cool-off period. Replying to the parent breaks threading and makes it annoying to read discussions ;).
That's the whole point of an array in Go. So you meant slices, not arrays.
Dynarray was slated for C++14 but has been pushed since it really isn't that useful and most people can get away with using vector.