Re:Go Statement Considered Harmful (2018)
by Jtsummers on Friday March 19, 2021 @01:58PM
(#26516405)
Go to the section "go statement considered harmful" itself. Specifically the subheading "Go statements break automatic resource cleanup".
He explicitly mentions join in that section. Specifically, not all of the concurrency libraries or language constructs offer a join-equivalent, and when they do it isn't language mandated that it is used. It remains "unstructured" and requires, like with his analogy to goto, careful use and monitoring by the programmer rather than getting language/library behavior guarantees.
He explicitly mentions join in that section. Specifically, not all of the concurrency libraries or language constructs offer a join-equivalent, and when they do it isn't language mandated that it is used. It remains "unstructured" and requires, like with his analogy to goto, careful use and monitoring by the programmer rather than getting language/library behavior guarantees.