Can the asymmetric barrier use the initialize/construct idiom?

[lars-t-hansen]

The various data types in parlib-simple use the initialize/construct idiom, where the shared memory is initialized by a static function on the data type and a constructor is then used uniformly in all agents to construct objects on top of that memory. The asymmetric-barrier does not use this idiom. In some sense that is appropriate since the data type is truly asymmetric. On the other hand it creates an extra cognitive load on use (?). We should investigate the possibility of making asymmetric-barrier stick closer to the common pattern, but we could hold off on this until other asymmetric data structures make it into this library (notably lock, condition, and buffer).

[lars-t-hansen]

The Par object (nee Multicore), which is also asymmetric, follows asymmetric-barrier here in that it has a MasterPar constructor and a WorkerPar constructor, but no initialize method. The MasterPar constructor initializes the shared memory and transmits it to the workers.