Thanks! So the scheduler serializes execution of critical sections? > In this case, messages are passed between work that contains the data. No locks are requ

Thanks! So the scheduler serializes execution of critical sections? > In this case, messages are passed between work that contains the data. No locks are required at the expense of memory footprint. Are messages copied or moved? If moved is there compile time checking for ownership or runtime debugging tools?