Joseph Schuchart

> In an older version i didn't used RegionCoords, but instead Dimensional to store the coordinates What's the reason to not use `Dimensional` to store the coordinates anymore?

@fuchsto I think we should merge this PR as is. Can you accept `RegionSpec` not being a `Dimensional`?

After having given this some more thought I modified the PR to *always* call into MPI for local memory accesses. If fast local access without progress is required the application...

Interesting use-case, didn't think we'd need that. Introducing that globally should be straight-forward (afaics, it's only relevant for `put`/`get`/`send`/`recv`/`sendrecv`, right?). Except for `sendrecv`, we can short-cut and avoid a call...

The `LoadBalancePattern` uses `TeamLocality` and the build fails because it's not const there: ``` cd /root/project/build-ci/20200302-153606--uuid-f5bf5f2c/clang/Release/build/dash && /usr/bin/clang++-5.0 -I/root/project/dash/include -I/root/project/dash/src -I/root/project/dart-if/include -I/opt/mpich/include -I/opt/papi/include -I/opt/phdf5/include -I/root/project/vendor/googletest/googletest/include -mtune=native -march=native -mfpmath=sse -fopenmp=libomp -O3...

On a more general note, I'm all in favor of making Team `const` where possible but that seems to be a bigger adventure :/

@bertwesarg I just added you to the developers group. You have to be logged in on CircleCI (with your Github credentials) to see the artifacts. Can you try again?

@fmoessbauer Yes, I agree. Any idea on why the other policies have been put in place originally?

Thanks for this brain dump! I think I get the idea. __On Execution Policies__ I think this is clear and it helps to get rid of some of the confusion...

> But on the other hand, how would you replace the current `dash::copy_async` by tasks? Not at all, it does not make sense to implement `dash::copy_async` in terms of tasks...