Skip to content
New issue

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

Incorrect __future class implementation #1776

Open
SergeyKopienko opened this issue Aug 12, 2024 · 0 comments
Open

Incorrect __future class implementation #1776

SergeyKopienko opened this issue Aug 12, 2024 · 0 comments
Assignees

Comments

@SergeyKopienko
Copy link
Contributor

__future(_Event __e, _Args... __args) : std::tuple<_Args...>(__args...), __my_event(__e) {}

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant