Some of the code assumes an arbitrary index type - but I was perhaps not always thorough or consistent and some places assume integer indexing.
Phases and collections in the MPI backend need to store a list of "local" indices. The MPI backend can only send/recv integer indices and track integer indices. Thus, when phases and collections wants to perform certain operations, their arbitrary index types must be "linearized" to an integer.
Create a 3D stencil example that used a tuple<int,int,int> as the index type.
Some of the code assumes an arbitrary index type - but I was perhaps not always thorough or consistent and some places assume integer indexing.
Phases and collections in the MPI backend need to store a list of "local" indices. The MPI backend can only send/recv integer indices and track integer indices. Thus, when phases and collections wants to perform certain operations, their arbitrary index types must be "linearized" to an integer.
Create a 3D stencil example that used a tuple<int,int,int> as the index type.