oneapi-src
[oneDPL][ranges] A fix for ranges::transform algo - it requires all input and output ranges to be sized.
A fix according to p3179r4. It requires all input and output ranges to be sized for ranges::transform algo.
It seems like we also need a fix for the oneDPL specification as well:
https://github.com/uxlfoundation/oneAPI-spec/blob/71f6bf676ca0b5d258373d499403f8738298e648/source/elements/oneDPL/source/parallel_api/parallel_range_api.rst?plain=1#L314
As for how to deal with any deprecation, or removal since it has already been released both in the spec and the code, it warrants some discussion.
Unfortunately, our specification diverges from recent P3179 updates in this regard and says that it's ok for just one range to be sized. Also in the long run it's likely that the standard will have a variation of || logic if the second range is infinite.
So I suggest not to proceed with this patch immediately and discuss what should be our best way forward. The same applies to equal and possibly mismatch.
