-
Notifications
You must be signed in to change notification settings - Fork 26
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
P1673R6 changes #186
P1673R6 changes #186
Conversation
1. Adopt P0009R13, which changes mdspan::operator[] to operator(). 2. Update references to P0009.
Apply fix from the following PR: ORNL#184
Remove references to any mdspan rank greater than 2. (These were left over from earlier versions of the proposal that included "batched" operations.) This should fix ORNL#143.
Change sum_of_squares to vector_sum_of_squares in comparison table. This should fix kokkos/stdBLAS#98 .
Replace "Requires" with "Preconditions," per new wording guidelines. This fixes kokkos/stdBLAS#95 .
Remove all overloads of `symmetric_matrix_rank_k_update` and `hermitian_matrix_rank_k_update` that do not take an `alpha` parameter. This prevents ambiguity between overloads that take `ExecutionPolicy&&` but not `alpha`, and overloads that take `alpha` but not `ExecutionPolicy&&`. This fixes kokkos/stdBLAS#134 .
Harmonize with the implementation, by adding `operator+`, `operator*`, and comparison operators to `conjugated_scalar`.
I don't think we should remove the overloads without alpha, its not ambiguous at all if you use the correct requires clauses. |
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.
I don't think we should remove the overloads - at least not without talking to all the other authors. There is no ambiguity here if you use the correct preconditions (i.e. C++20 requires clauses).
I'll put them back in the next version. That was a bit of a hasty decision. On the other hand, the ambiguity would be challenging to resolve without some complicated In any case, I submitted this as R6, so please do merge it. I can file an issue to bring back the overloads, if we can figure out how to constrain them correctly. |
Superseded by PR #222 . Thanks! |
Merge of #222 means we can delete this branch. |
Changes for P1673R6.