Re: [Boost-users] Compiler limitation (MSVS 2015 update 2) or real error using boost::async?

Subject: Re: [Boost-users] Compiler limitation (MSVS 2015 update 2) or real error using boost::async?
From: Juan Ramírez (jramirez.uy_at_[hidden])
Date: 2016-05-05 13:02:10

Based on this
<http://www.boost.org/doc/libs/1_52_0/doc/html/thread/synchronization.html#thread.synchronization.futures.reference.async>
doc, boost::async is defined as follows:

template <class F>
 future <http://www.boost.org/doc/libs/1_52_0/doc/html/thread/synchronization.html#thread.synchronization.futures.reference.unique_future><typename
result_of<typename decay<F>::type()>::type>async(F f);template <class
F>
 future <http://www.boost.org/doc/libs/1_52_0/doc/html/thread/synchronization.html#thread.synchronization.futures.reference.unique_future><typename
result_of<typename decay<F>::type()>::type>async(launch policy, F f);

In your example you are calling the second overload, which takes a launch
policy in its first argument, boost::launch is an enum (se here
<http://www.boost.org/doc/libs/1_58_0/boost/thread/futures/launch.hpp>), i
guess the compiler is failing trying to create an enum from your class
instance.

I tried  your example using boost::launch::async and capturing your tex
object: didn't have any problems at all.

Best regards,
Juan

On Thu, May 5, 2016 at 9:18 AM, James Swift <james_at_[hidden]> wrote:

> Hi,
>
> in case anyone wants to play with the example I provided but doesn't have
> access to MSVC you can do so online here.
>
> http://rextester.com/BAX37541
>
> kind regards,
> James
>
>
> _______________________________________________
> Boost-users mailing list
> Boost-users_at_[hidden]
> http://lists.boost.org/mailman/listinfo.cgi/boost-users
>

-- 
Juan
:wq