On Fri, 17 Mar 2017 21:10:18 GMT, Carl Sturtivant wrote:

On Fri, 17 Mar 2017 21:09:12 +0100, Sönke Ludwig wrote:

Starting computation in main task
Starting to compute value in worker task.
Finished computation in main task. Waiting for async value.
CoreTaskFiber was terminated unexpectedly: Joining tasks in foreign threads is currently not supported.
Program exited with code 255

Any chance this could get fixed? I was seriously relying on this feature working; it was mentioned the introductory book as working, and the online docs don't indicate a difficultly, so I incorrectly thought async was working.

This should be fixed/implemented for the new vibe-core package, which
is not yet the default in 0.8.0. Try adding this to the package recipe
to force using vibe-core:

dependency "vibe-d:core" version="~>0.8.0-beta"
subConfiguration "vibe-d:core" "vibe-core"

I tried this, paranoiacally ran dub upgrade and dub --force and got the same error.

Apologies, not so, I didn't have the configuration exactly right. Now it doesn't do that. It runs and does not terminate with an error, just hangs. After 10 seconds I hit ^C. When I attempted to rerun via dub it could not listen on the same port. Here's the output.

[vibe-0(M3JX) INF] Starting to compute value in worker task.
[main(nDQ8) INF] Starting computation in main task
[main(nDQ8) INF] Finished computation in main task. Waiting for async value.
^C
carl@carl1604:~/Documents/vibed/asynctest$ [main(nDQ8) INF] [main(----) INF] Received signal 2. Shutting down.

I'll try running it again.