mirror of
https://gitlab.kitware.com/vtk/vtk-m
synced 2024-09-08 21:33:55 +00:00
7811cc4b1e
Many of the fancy `ArrayHandle`s are read-only and therefore connot really create write portals. Likewise, many `ArrayHandle`s (both read- only and read/write) have no way to resize themselves. In this case, implementing the `CreateWritePortal` and `ResizeBuffers` methods in the `Storage` class was troublesome. Mostly they just threw an exception, but they also sometimes had to deal with cases where the behavior was allowed. To simplify code for developers, this introduces a pair of macros: `VTKM_STORAGE_NO_RESIZE` and `VTKM_STORAGE_NO_WRITE_PORTAL`. These can be declared in a `Storage` implementation when the storage has no viable way to resize itself and create a write portal, respectively. Having boilerplate code for these methods also helps work around expected behavior for `ResizeBuffers`. `ResizeBuffers` should silently work when resizing to the same size. Also `ResizeBuffers` should behave well when resizing to 0 as that is what `ReleaseResources` does.
46 lines
1.2 KiB
C++
46 lines
1.2 KiB
C++
//============================================================================
|
|
// Copyright (c) Kitware, Inc.
|
|
// All rights reserved.
|
|
// See LICENSE.txt for details.
|
|
//
|
|
// This software is distributed WITHOUT ANY WARRANTY; without even
|
|
// the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR
|
|
// PURPOSE. See the above copyright notice for more information.
|
|
//============================================================================
|
|
|
|
#include <vtkm/cont/Storage.h>
|
|
|
|
namespace vtkm
|
|
{
|
|
namespace cont
|
|
{
|
|
namespace internal
|
|
{
|
|
namespace detail
|
|
{
|
|
|
|
void StorageNoResizeImpl(vtkm::Id currentNumValues,
|
|
vtkm::Id requestedNumValues,
|
|
std::string storageTagName)
|
|
{
|
|
if (currentNumValues == requestedNumValues)
|
|
{
|
|
// Array resized to current size. This is OK.
|
|
}
|
|
else if (requestedNumValues == 0)
|
|
{
|
|
// Array resized to zero. This can happen when releasing resources.
|
|
// Should we try to clear out the buffers, or avoid that for messing up shared buffers?
|
|
}
|
|
else
|
|
{
|
|
throw vtkm::cont::ErrorBadAllocation("Cannot resize arrays with storage type of " +
|
|
storageTagName);
|
|
}
|
|
}
|
|
|
|
}
|
|
}
|
|
}
|
|
} // namespace vtkm::cont::internal::detail
|