Notes on structured concurrency, or: Go statement considered harmful (2018)
1–3 of 3 posts
Re: Notes on structured concurrency, or: Go statement considered harmful (2018)
#2[deleted]
Re: Notes on structured concurrency, or: Go statement considered harmful (2018)
#3Seven years later, and the sort of fan out/in behavior proposed here is implemented all the time where necessary but not considered a concurrency primitive. I think I remain more interested in the erlang/elixir process approach to concurrency. Practically that seems so much more powerful than anything else available today.