-
Notifications
You must be signed in to change notification settings - Fork 68
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
merge_sort #11
Comments
Unless, it's explicitly stated otherwise, input and output iterators must point to separate memory (separate ranges). |
Thank you for your answer. Is radix_sort and/or merge_sort stable? I cannot find anything in the docs about it, however, in the tests, you are comparing to std::stable_sort. |
Radix sort is stable. Merge sort is not. |
Thank you very much! I have one more question: |
I don't think that's possible. |
I am not sure if that is possible, with integers |
Yes, right now it's not possible. It would require some changes to radix sort implementation (it's doable). Right now there are not plans to do them. |
Does device wide merge_sort support in-place sorting (keys_input == keys_output and values_input == values_output)?
What about radix sort? I guess it does not support in-place sorting, but I could not find anything in the docs about it.
The text was updated successfully, but these errors were encountered: