boostorg / boostorg/sort

Additional memory specification does not seem to consider the index for block indirect sort

Open
#70 5 comments 0 reactions 1 assignee Claimed by @fjtapia View on GitHub
Dominant language
C++
Stars
58
Forks
47
PR merge metrics
No merged PRs in 30d

Description

Reading the paper about block indirect sort I was very puzzled of how one could manage the blocks indirectly without some sort of index, whose size would have been linear in the data (very small, like below 1%, but still depending on the data, not on the number of threads). Looking at the code, it seems to me that the variable `std::vector index` of the backbone is in fact a vector of additional `usize` values of length equal to the number of blocks. Am I correct?

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.