Hi everyone,
The pull request 'Compile time launch policies'
(https://github.com/STEllAR-GROUP/hpx/pull/2276) is about to be merged to
the master branch of our repository. This will introduce a breaking change
for a handful of API functions exposed by HPX.
This PR will affect all of those functions which so far had names ending in
'_sync' or '_async' to distinguish two separate versions of functions for
the same functionality, one for synchronous operation and the other for
asynchronous operation (usually returning a future object). These functions
now have been replaced by functions using the same name for the sync/async
versions, they now however expect to be called with an explicit launch
policy, such a hpx::launch::sync or hpx::launch::async.
In short, if a function was invoked before as
T val = foo_sync(args...);
it now has to be invoked as
T val = foo(hpx::launch::sync, args...);
Equivalently, any function previously invoked as
future<T> f = bar_async(args...);
now has to be called as
future<T> f = bar(hpx::launch::async, args...);
In the short term, the old function overloads can be brought back by setting
the `HPX_WITH_ASYNC_FUNCTION_COMPATIBILITY` CMake option.
Regards Hartmut
---------------
http://boost-spirit.com
http://stellar.cct.lsu.edu
_______________________________________________
hpx-users mailing list
[email protected]
https://mail.cct.lsu.edu/mailman/listinfo/hpx-users
