So, all the comments are about reinterpret_cast/bit_cast. The issues is that our algorithms require running algorithms or constructing ArborX geometry types from some other types. Often, these other types are provided by a user, and we convert them to something that internally we can digest. We could follow boost and explicitly construct internal data by using getters.
I think this is a larger discussion and is outside of the scope of this PR.
So, all the comments are about
reinterpret_cast
/bit_cast
. The issues is that our algorithms require running algorithms or constructing ArborX geometry types from some other types. Often, these other types are provided by a user, and we convert them to something that internally we can digest. We could follow boost and explicitly construct internal data by using getters.I think this is a larger discussion and is outside of the scope of this PR.