Sorry copy and paste failed
Nothing bad about std.parallelism. vibe.d just uses a more fine-grained
approach where a task is based on a fiber, whereas std.parallelism has
monolithic tasks that block a thread as long as they run. But hopefully
Could you explain this a bit more? When would you need to interrupt a task?
I have done a few experiments myself with std.parallelism and it seems that when a task has to wait for another task to finish, it will reschedule that task instead of blocking that thread.
The only thing that seems to be missing is some sort of priority system.