News for hackers. Stuff that matters.
Re:Why Threads are a Bad Idea (for most purposes) (1995) [pdf] by chrisseaton on Tuesday June 13, 2017 @06:34PM (#14549250)
Yes you can build fork-join that way, but you'd need to remember to manually follow some rules. You should create the tasks a and b immediately before you await, and do no other work between creating them and awaiting. And you should not cause any side effects in the two tasks.

Systems which have fork-join built-in would either help you to follow those rules, or force you to.

Re:Why Threads are a Bad Idea (for most purposes) (1995) [pdf] by mamcx on Tuesday June 13, 2017 @10:35PM (#14550325)
So, if I understand, you "tasks" are almost pure functions:

   fork -> send -> task1(input) & task2(input) -> joiner
And you must always(?) have a join? so I can't have a zombie task elsewhere?

I probably like how this sound! Exist a more detailed material to study on this?