Randolph Settgast

Duh. I guess we would have to wait until we have compile-time dims added.

Did you ever put together a proposal for compile time dims, or are we waiting for RAJA to do it first?

I still think it is worth doing and just adding to the deducable types when they become available. I just really dislike having to specify the dims for something that...

> Note: code in GEOSX that uses this is currently disabled behind an `#if 0`, because I found out some Tpetra-based solvers only work reliably with Unified Memory, and so...

> > Do we need to update Trilinos? > > No, there's no new version available. And it's not something they seem to have fixed yet. All Tpetra build instructions,...

> for( int i = 0; i < NDIM; ++i ) > { > m_dataBuffers[ i ] = std::move( views[ i ].m_dataBuffer ); > } > } That should be??...

OK. that looks nice. I guess we don't need anything to help with the creation of the multi view as the `createMultiView` is pretty simple...but we can add a variadic...

After working with it a bit, I am pretty sure this is not the desired behavior. It seems a bit arbitrary where to move the data, and the fact that...

@corbett5 @klevzoff After debugging the topology change routines in GEOSX, I am certain that something needs to be done to assist the user of LvArray with this. Let us not...

How about adding an `open()` and `close()` method, with 2 bool members `m_closed`, and `m_didRealloc`. Prior to any reallocation, we would have to call `open()`. This would: 1. make sure...