vtk-m/vtkm/cont/cuda
Robert Maynard c123796949 VTK-m ArrayHandle can now take ownership of a user allocated memory location
Previously memory that was allocated outside of VTK-m was impossible to transfer to
VTK-m as we didn't know how to free it. By extending the ArrayHandle constructors
to support a Storage object that is being moved, we can clearly express that
the ArrayHandle now owns memory it didn't allocate.

Here is an example of how this is done:
```cpp
  T* buffer = new T[100];
  auto user_free_function = [](void* ptr) { delete[] static_cast<T*>(ptr); };

  vtkm::cont::internal::Storage<T, vtkm::cont::StorageTagBasic>
      storage(buffer, 100, user_free_function);
  vtkm::cont::ArrayHandle<T> arrayHandle(std::move(storage));
```
2018-04-04 11:28:25 -04:00
..
internal VTK-m StorageBasic is now able to give/take ownership of user allocated memory. 2018-04-04 11:27:57 -04:00
testing VTK-m ArrayHandle can now take ownership of a user allocated memory location 2018-04-04 11:28:25 -04:00
ChooseCudaDevice.h Enable highest level of warnings(W4) under MSVC 2017-09-22 13:04:28 -04:00
CMakeLists.txt Update copyright for Sandia 2017-09-20 15:33:44 -06:00
DeviceAdapterCuda.h Update copyright for Sandia 2017-09-20 15:33:44 -06:00
ErrorCuda.h Update copyright for Sandia 2017-09-20 15:33:44 -06:00