oneDPL
oneDPL copied to clipboard
Rely on CTAD in the implementation of c++20 ranges algorithms
Can we not write this ugly `decltype`? I hope CTAD should help us here. If __tranform_functor is an aggregate, let's write our deduction guide. What do you think?
Originally posted by @rarutyun in https://github.com/oneapi-src/oneDPL/pull/1457#discussion_r1687495468