Better to specify the amount of results for __result_and_scratch_storage_impl at compile-time

[SergeyKopienko]

I think probably better to specify the amount of results for __result_and_scratch_storage_impl at compile-time:

• please take a look to

  oneDPL/include/oneapi/dpl/pstl/hetero/dpcpp/parallel_backend_sycl_utils.h

  Line 578 in e90b267

  __result_and_scratch_storage_impl(const _ExecutionPolicy& __exec_, std::size_t __result_n, std::size_t __scratch_n)

  for details.

From my point of view it's implementable and as also we can also return results from __result_and_scratch_storage_impl - I seen some requests for that from @MikeDvorskiy side in his PRs.

Of course, I propose that only for std::size_t __result_n parameter, not for std::size_t __scratch_n parameter.

As some benefit of this approach we able to return std::tuple from __result_and_scratch_storage_impl when it contains more then one result inside.

[akukanov]

Seems this is already implemented. @SergeyKopienko is it OK to close the discussion, or is there more to consider?

[SergeyKopienko]

Yes, sure. It was implemented in the PR #2167