未存储返回值时,std::async 不会产生新线程 [英] std::async won't spawn a new thread when return value is not stored

查看:28
本文介绍了未存储返回值时,std::async 不会产生新线程的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

考虑我有lamba foo 它只做一些事情并且不需要返回任何东西.当我这样做时:

Consider I have lamba foo which just does some stuff and doesn't need to return anything. When I do this:

std::future<T> handle = std::async(std::launch::async, foo, arg1, arg2);

一切正常,lamba 将在新线程中生成.但是,当我不存储 std::async 返回的 std::future 时,foo 将在主线程中运行并阻塞它.>

Everything runs fine and the lamba will be spawned in a new thread. However, when I don't store the std::future which the std::async returns, the foo will be run in the main thread and block it.

std::async(std::launch::async, foo, arg1, arg2);

我在这里遗漏了什么?

推荐答案

来自 just::thread 文档:

如果策略是 std::launch::async 然后在它自己的线程上运行 INVOKE(fff,xyz...).当该线程完成时,返回的 std::future 将准备就绪,并将保存函数调用抛出的返回值或异常.与返回的 std::future 的异步状态相关联的最后一个 future 对象的析构函数应阻塞,直到 future 准备好.

If policy is std::launch::async then runs INVOKE(fff,xyz...) on its own thread. The returned std::future will become ready when this thread is complete, and will hold either the return value or exception thrown by the function invocation. The destructor of the last future object associated with the asynchronous state of the returned std::future shall block until the future is ready.

std::async(std::launch::async, foo, arg1, arg2);

返回的 future 不会在任何地方赋值,它的析构函数会阻塞直到 foo 完成.

The returned future is not assigned anywhere and its destructor blocks until foo finishes.

这篇关于未存储返回值时,std::async 不会产生新线程的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆