We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
__future
oneDPL/include/oneapi/dpl/pstl/hetero/dpcpp/parallel_backend_sycl_utils.h
Line 700 in e2e6ffd
As we may see at https://en.cppreference.com/w/cpp/thread/future/future and https://en.cppreference.com/w/cpp/thread/future/operator%3D, the std::future implementation has deleted copy-constructor and copy-assignment : only move-constructor and move-assignment supported.
std::future
I believe we forgot to implement these restrictions in oneDPL implementation of __future.
oneDPL
The text was updated successfully, but these errors were encountered:
sycl::event
__result_and_scratch_storage
SergeyKopienko
No branches or pull requests
oneDPL/include/oneapi/dpl/pstl/hetero/dpcpp/parallel_backend_sycl_utils.h
Line 700 in e2e6ffd
As we may see at https://en.cppreference.com/w/cpp/thread/future/future and https://en.cppreference.com/w/cpp/thread/future/operator%3D, the
std::future
implementation has deleted copy-constructor and copy-assignment : only move-constructor and move-assignment supported.I believe we forgot to implement these restrictions in
oneDPL
implementation of__future
.The text was updated successfully, but these errors were encountered: