This PR moves the process implementation from pkg/process to pkg/csp, along side the channel implementation. There are no functional changes.
@mikelsr The rationale is that Wetware logically bundles processes and channels together in the "communicating sequential processe" (CSP) model of concurrency-control. The API assumes that processes and channels go together in the same way that Go associates goroutines and channels, so it makes sense that they would live in the same package. Plus,csp.Proc and csp.Chan is nice and terse 😄
This will simplify the package structure when we start to add the low-level imports & exports needed for our cluster syscall API.
This PR moves the process implementation from
pkg/processtopkg/csp, along side the channel implementation. There are no functional changes.@mikelsr The rationale is that Wetware logically bundles processes and channels together in the "communicating sequential processe" (CSP) model of concurrency-control. The API assumes that processes and channels go together in the same way that Go associates goroutines and channels, so it makes sense that they would live in the same package. Plus,
csp.Procandcsp.Chanis nice and terse 😄This will simplify the package structure when we start to add the low-level imports & exports needed for our cluster syscall API.