Hmmm...as far as I understood the FA, the point is exactly that 'go' is
unlike PAR in important respects.
'go' is more like a goto, the new goroutine is spawned, without any scoping. PAR opens a scope where all the contained routines are executed in parallel, but all of these must have terminated before the statement after the PAR is executed.
?