duandai2178 2019-01-11 18:33
浏览 78
已采纳

sync.Waitgroup不会阻止执行

Consider this code snippet

package main

import (
    "fmt"
    "sync"
    "time"
)

func main() {
    wg := new(sync.WaitGroup)
    nap := func() {
        wg.Add(1)
        time.Sleep(2 * time.Second)
        fmt.Println("nap done")
        wg.Done()
    }

    go nap()
    go nap()
    go nap()

    fmt.Println("nap time")
    wg.Wait()
    fmt.Println("all done")
}

Running such code gives expected output:

nap time
nap done
nap done
nap done
all done

Now let's ommit first standard output print before wg.Wait():

// fmt.Println("nap time")
wg.Wait()
fmt.Println("all done")

The output now changes to unexpected:

all done

Where expected would be:

nap done
nap done
nap done
all done

Same code on the playground does give this output without a need of omitting the stdout print.

Can you explain to me, what I am missing there?

  • 写回答

1条回答 默认 最新

  • duanniedang3946 2019-01-11 18:33
    关注

    Even though this looks like magic, it has a logical explanation. Go doesn't guarantee the order of goroutines execution. There are three goroutines spawned in given snippet code, but in fact, there are four of them: the very first one that is spawned when the execution starts.

    Stdout print is omitted

    This goroutine spawned three nap functions and continued in its plan. It was so fast that it executed wg.Wait() before any of spawned goroutines was able to call wg.Add(1). As a result wg.Wait() didn't block the execution and program ended.

    Print to stdout before wg.Wait()

    In this case, program execution was different, goroutines were able to make wg.Add(1) call because the main goroutine wasn't fast as in the first case. This behavior isn't guaranteed, which can be seen in the linked playground example.

    It has nothing to do with stdout print

    The following code sample will give the same expected output:

    time.Sleep(time.Second)
    wg.Wait()
    fmt.Println("all done")
    

    The fmt.Println() had the same impact as time.Sleep() had.

    Idiomatic way

    The rule is simple: call wg.Add(1) before spawning the goroutine.

    package main
    
    import (
        "fmt"
        "sync"
        "time"
    )
    
    func main() {
        wg := new(sync.WaitGroup)
        nap := func() {
            time.Sleep(2 * time.Second)
            fmt.Println("nap done")
            wg.Done()
        }
    
        napCount := 3
        wg.Add(napCount)
        for i := 0; i < napCount; i++ {
            go nap()
        }
    
        wg.Wait()
        fmt.Println("all done")
    }
    
    本回答被题主选为最佳回答 , 对您是否有帮助呢?
    评论

报告相同问题?

悬赏问题

  • ¥15 Arcgis相交分析无法绘制一个或多个图形
  • ¥15 seatunnel-web使用SQL组件时候后台报错,无法找到表格
  • ¥15 fpga自动售货机数码管(相关搜索:数字时钟)
  • ¥15 用前端向数据库插入数据,通过debug发现数据能走到后端,但是放行之后就会提示错误
  • ¥30 3天&7天&&15天&销量如何统计同一行
  • ¥30 帮我写一段可以读取LD2450数据并计算距离的Arduino代码
  • ¥15 飞机曲面部件如机翼,壁板等具体的孔位模型
  • ¥15 vs2019中数据导出问题
  • ¥20 云服务Linux系统TCP-MSS值修改?
  • ¥20 关于#单片机#的问题:项目:使用模拟iic与ov2640通讯环境:F407问题:读取的ID号总是0xff,自己调了调发现在读从机数据时,SDA线上并未有信号变化(语言-c语言)