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

Unwrapped issue with future<void> #1528

Closed
K-ballo opened this issue May 19, 2015 · 0 comments

Comments

Projects
None yet
2 participants
@K-ballo
Copy link
Member

commented May 19, 2015

Variadic unwrapped has introduced a regression for the future-ranges case. When the future value type is void, the implementation tries to instantiate tuple<void>. The following snippet reproduces the issue:

std::vector<hpx::future<void>> fs;
hpx::util::unwrapped(&noop)(fs);

K-ballo added a commit to K-ballo/hpx that referenced this issue May 19, 2015

Fix unwrapped issue with future ranges of void type
The implementation tried to instantiate `tuple<void>`, which was a synonym for `tuple<>` under the faux variadic implementation but is a hard error with true variadics. Fixes STEllAR-GROUP#1528

@hkaiser hkaiser added this to the 0.9.11 milestone May 19, 2015

K-ballo added a commit to K-ballo/hpx that referenced this issue May 19, 2015

Fix unwrapped issue with future ranges of void type
The implementation tried to instantiate `tuple<void>`, which was a synonym for `tuple<>` under the faux variadic implementation but is a hard error with true variadics. Fixes STEllAR-GROUP#1528
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.