las3_pub / predictable_parallel_patterns

This was highlighted as an issue in the steal_work routine, as frequent calls to virtual functions are expensive.

We do this to properly separate the cache alginment logic in the next step, allowing us to port all cache aligned objects without worrying about portability.

This lead to some bug-fixes that covered move constructors not correctly assigning memory. We might clean this up further by only allowing in place creation of these types (placement new).