Skip to content

Correct type for the output portal in DeviceAdapterAlgorithmGeneral::UpperBounds

Will Usher requested to merge Twinklebear/vtk-m:fix-upper-bounds-out-type into master

It looks like the type here was accidently written as a ArrayHandle<T, COut> when it should (I think) be ArrayHandle<vtkm::Id, COut>. I Encountered this causing a compilation error when trying to run some benchmarks with FloatDefault input and values since it was using the wrong type for some iterators if I recall correctly and couldn't cast to the vtkm::Id type. This should fix that by using the correct type for the output portal.

Merge request reports