[oneDPL][ranges] support size limit for output for merge algorithm #1942
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
MikeDvorskiy
force-pushed
the
dev/mdvorski/merge_sized_output
branch
9 times, most recently
from
33cd332 to
d443dbe
Compare
MikeDvorskiy
force-pushed
the
dev/mdvorski/merge_sized_output
branch
4 times, most recently
from
9ebcfb6 to
0066210
Compare
MikeDvorskiy
force-pushed
the
dev/mdvorski/merge_sized_output
branch
7 times, most recently
from
3f648a7 to
5b078ad
Compare
…rn (based on merge path) for host back-ends
…rge path for the host backend (__pattern_merge_2)
…r_backend::__parallel_for
…erge sycl pattern support
…_pattern_merge, (SYCL backend)
MikeDvorskiy
force-pushed
the
dev/mdvorski/merge_sized_output
branch
from
98a7acb to
c81b4c1
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
[oneDPL][ranges] support size limit for output for merge algorithm.
The change is according to https://www.open-std.org/jtc1/sc22/wg21/docs/papers/2024/p3179r2.html#range_as_output
Update: Changes to draft status, causing faced to design issue, connected with different return types from the merge patterns -
__result_and_scratch_storage/__result_and_scratch_storage_base. As an option - to have one common type of __result_and_scratch_storage for the all needs (ate least for pattern dpcpp merge patterns).