Depends on node-dot-cpp/memory-safe-cpp#32 .
Noderoutines are portions of code which MAY be executed in a different thread (implementing "offloading" from Vol. II of DDoMOG). UNLIKE goroutines, noderoutines are 100% Shared-Nothing.
Expected Usage:
co_await noderoutine([](){...})
IMPORTANT: All noderoutine parameters AND all noderoutine captures MUST be self-contained types passed BY VALUE (which MUST be enforced by static checker, details TBD)
TBD: temp_const<>
Implementation-wise, for the time being we can simply send noderoutines to thread pool (it is INEFFICIENT, but correct; efficient implementation belongs to issue #44).
Depends on node-dot-cpp/memory-safe-cpp#32 .
Noderoutines are portions of code which MAY be executed in a different thread (implementing "offloading" from Vol. II of DDoMOG). UNLIKE goroutines, noderoutines are 100% Shared-Nothing.
Expected Usage:
co_await noderoutine([](){...})IMPORTANT: All noderoutine parameters AND all noderoutine captures MUST be self-contained types passed BY VALUE (which MUST be enforced by static checker, details TBD)
TBD:
temp_const<>Implementation-wise, for the time being we can simply send noderoutines to thread pool (it is INEFFICIENT, but correct; efficient implementation belongs to issue #44).