You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
for( int i = 0; i < NDIM; ++i )
{
m_dataBuffers[ i ] = std::move( views[ i ].m_dataBuffer );
}
}
That should be??
for( int i = 0; i < NARRAYS; ++i )
{
m_dataBuffers[ i ] = std::move( views[ i ].m_dataBuffer );
}
Looks pretty straight forward. The combination of different T would be essential to general usage....which would make it much less straight forward I guess.
Yeah internally it would be a bit more complicated using a tuple instead of an array for m_dataBuffers. The usage would be pretty much the same. You'd have to call toSlice< 0 >() instead of toSlice( 0 ), but that's fine. As for construction we could create a
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 macro to ease the definition of all the slices.
Make something similar to the RAJA MultiView. Here's what I imagine it would look like.
Would need to be a bit more complicated to ensure the same copy-semantics as
ArrayView
.With a little work it could be extended to support views with different types, which would be necessary if you want to mix
T
withT const
.Usage would look something like
The text was updated successfully, but these errors were encountered: