For loop

 The Go for loop is similar to—but not the same as—C's. It unifies for and while and there is no do-while. There are three forms, only one of which has semicolons.

// Like a C for
for init; condition; post { }

// Like a C while
for condition { }

// Like a C for(;;)
for { }

Short declarations make it easy to declare the index variable right in the loop.

sum := 0
for i := 0; i < 10; i++ {
    sum += i
}

If you're looping over an array, slice, string, or map, or reading from a channel, a range clause can manage the loop.

for key, value := range oldMap {
    newMap[key] = value
}

If you only need the first item in the range (the key or index), drop the second:

for key := range m {
    if key.expired() {
        delete(m, key)
    }
}

If you only need the second item in the range (the value), use the blank identifier, an underscore, to discard the first:

sum := 0
for _, value := range array {
    sum += value
}

Comments

Post a Comment

Popular posts from this blog

Naming convention

  Interface names By convention, one-method interfaces are named by the method name plus an -er suffix or similar modification to construct an agent noun:  Reader ,  Writer ,  Formatter ,  CloseNotifier  etc. MixedCaps Finally, the convention in Go is to use  MixedCaps  or  mixedCaps  rather than underscores to write multiword names. Getters It's neither idiomatic nor necessary to put  Get  into the getter's name. If you have a field called  owner  (lower case, unexported), the getter method should be called  Owner  (upper case, exported), not  GetOwner . The use of upper-case names for export provides the hook to discriminate the field from the method. A setter function, if needed, will likely be called  SetOwner . Both names read well in practice: owner := obj.Owner() if owner != user {     obj.SetOwner(user) } They even have semantic effect: the visibility of a name outside a package i...
Read more