-
Notifications
You must be signed in to change notification settings - Fork 407
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Move Kokkos::reduction_identity
into its own header file
#5450
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
looks good.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Let's see if someone complains. In the end, reduction_identity
should only be relevant if people call parallel_reduce
but, of course, they might just have included this header for specializing reduction_identity
. Anyway, if we merge early, we can hope that users complain early and it would be easy to revert.
I was not clear enough. We know that it will break code downstream (for instance edit actually I looked closer and it wouldn't actually break KokkosKernels. The source files that use |
If this breaks too many projects, we could, of course, include |
I would only consider it if guarded with |
I think it's a good change but we should deprecate the current code since we know it will break user code. |
…> for backward compatibility
OK as a compromise what if I include the new |
Move
reduction_identity
from<Kokkos_NumericTraits.hpp>
to a new (public?) header<Kokkos_ReductionIdentity.hpp>
Admittedly this may break code downstream :/