Calling async with a function pointer to a function with return type void leads to a compilation error. Not sure if this counts as a bug, as in general a return value might reasonably be expected.
Am 17.03.2017 um 17:19 schrieb Carl Sturtivant:
Calling async with a function pointer to a function with return type void leads to a compilation error. Not sure if this counts as a bug, as in general a return value might reasonably be expected.
The API is currently not completely appropriate for this use case
("getResult"), but apart from that, this would be a valid
generalization. It is of course equivalent to using run(Worker)Task
directly, so I wouldn't exactly prioritize its implementation given the
plethora of other open issues.
On Fri, 17 Mar 2017 21:32:36 +0100, Sönke Ludwig wrote:
Am 17.03.2017 um 17:19 schrieb Carl Sturtivant:
Calling async with a function pointer to a function with return type void leads to a compilation error. Not sure if this counts as a bug, as in general a return value might reasonably be expected.
The API is currently not completely appropriate for this use case
("getResult"), but apart from that, this would be a valid
generalization. It is of course equivalent to usingrun(Worker)Task
directly, so I wouldn't exactly prioritize its implementation given the
plethora of other open issues.
I think it's not really a bug. I can return bool. :)