vtk-m/vtkm
Kenneth Moreland 2f781dfe7a Preserve data in ArrayHandle::ReleaseResourcesExecution
Previously when ReleaseResourcesExecution was called, the method blindly
deleted the execution array regardless of whether there was a valid copy
in the control environment. This could potentially lose data. What if
someone wanted to conserve memory on the device by clearing the array of
an output array?

There is also now an internal method that blindly deletes the array.
This is good for internal functions that are doing something to
invalidate the execution data anyway.
2015-02-10 15:49:55 -07:00
..
cont Preserve data in ArrayHandle::ReleaseResourcesExecution 2015-02-10 15:49:55 -07:00
exec The DoWorkletInvokeFunctor methods were missing VTKM_EXEC_EXPORT. 2015-01-15 22:47:28 -07:00
internal Move another FunctionInterface manipulation to be exclusively control 2015-01-15 22:42:36 -07:00
testing Update the documentation to note have references to dax. 2014-12-10 10:37:25 -05:00
worklet Move the MapField testing worklets to a worklet namespace. 2015-01-19 14:25:54 -05:00
CMakeLists.txt Add ability to zip function interface objects. 2014-10-16 16:31:55 -06:00
Extent.h Change vtkm::Tuple to vtkm::Vec 2014-10-08 10:09:43 -06:00
ListTag.h Add a template that tests whether a type is in a list. 2014-10-22 10:35:56 -06:00
Pair.h Add utility include to Pair.h 2014-10-23 16:34:52 -06:00
TypeListTag.h Add a template that tests whether a type is in a list. 2014-10-22 10:35:56 -06:00
Types.h Adding a cuda device adapter to vtkm. 2014-12-19 13:47:28 -05:00
TypeTraits.h Remove vtkm::Scalar and vtkm::Vector# types 2014-10-09 08:54:56 -06:00
VecTraits.h Change VectorTraits to VecTraits. 2014-10-08 10:09:43 -06:00