Alexey Kukanov

@upsj. while we still evaluating the idea for `transform_output_iterator`, for the particular example with dropping an element out of a tuple you can use the combination of `zip_iterator` and `discard_iterator`.

A good practice is to describe the purpose of a patch - what problem(s) it intends to solve, etc. This patch has no description at all. Also I am always...

Yes, DPC++ should have the new header: https://github.com/intel/llvm/blob/sycl/sycl/include/sycl/sycl.hpp I agree that changing oneDPL to use the new header is the right way to go.

@amallia, it is better to contribute to the upstream Parallel STL project maintained within LLVM.

Does this change introduce any new dependencies for either compilation/link time or execution time which need to be documented? Do we know that the dispatch semaphore has no spurious wakeups?

Let's start writing some meaningful descriptions to PRs. What's the motivation for this change, and why we think it's appropriate? Ruslan asked: "Is there any precedence for those functions not...

> Current comment state was made by me like @akukanov proposed, as far as I understood his proposal. It was Mikhail's proposal, actually, as he said "I would place the...

Addressed in v1.2 specification

This patch is interesting but needs some more work. In particular, I think the semantics of transform_if should follow that of the regular transform algorithm, just extending it with the...

This implementation has been integrated into LLVM PSTL codebase and taken into oneDPL from there.