Make all algorithms in cuda/std/algorithm available through cuda/std/algorithm.meow

[miscco]

We had a poll to see how users would like to access individual features of umbrella headers like <cuda/std/algorithm>

The vast majority preferred a pattern like <cuda/std/algorithms/find.h>

However, we can get away with finding a similar but different name if we use the pattern umbrella_header.feature

We can create a wrapper for the internal file and also instruct our IDE to ignore all files that match the pattern [a-z_]*\.[a-z_]* This works because we do not have any .h files in neither <cuda/> not <cuda/std/>

[miscco]

I am proposing to keep the current folder structure intact and only add symlinks EDIT: discussed this internally and we need real files for windows

For me this greatly improves maintainability of our code base. Otherwise there are 500+ files in <cuda/std/> and no proper way of organizing them

[miscco]

Note this one here might be a tad dangerous, it also removes the files for search paths in the VS-code IDE

We might want to drop that

[jrhemstad]

Can you elaborate on this? What was this added for?

[miscco]

These additional files add a considerable maintenance burden on the cuda/std folder.

What is now relatively well contained will contain a few hundred headers soon. vs-code and other IDEs offer exclude files, where one can hide those files.

vs-code in particular has 2 options

• hide files from explorer view
• hide files from search view -> searching in the repository will not show those files

[jrhemstad]

I am proposing to keep the current folder structure intact and only add symlinks

I don't think symlinks work on Windows, do they?

[jrhemstad]

Given this is a pretty extensive product facing change, I'd like more thoughts from @wmaxey @griwes @gevtushenko @brycelelbach @ericniebler

[miscco]

I am proposing to keep the current folder structure intact and only add symlinks

I don't think symlinks work on Windows, do they?

They dont, moved to forwarding headers

[github-actions]

😬 CI Workflow Results

🟥 Finished in 1h 23m: Pass: 99%/453 | Total: 4d 05h | Max: 55m 56s | Hits: 99%/515395

See results here.

[jrhemstad]

Some questions I'd like answered before we merge this:

• How will we test this? I think we should have tests that include each micro-header and ensure that was is supposed to be available in that header is indeed available.
• How will we document this?
• I'd like to see an evaluation of how well this naming pattern will extend to other headers