[RFC] What should we call our shared concurrent algos library?

[iwoplaza]

Stuff like concurrent scan and sort would become part of it

Ideas:

• @typegpu/algo
• @typegpu/scan
• @typegpu/math

[reczkok]

@typegpu/sort

[aleksanderkatan]

I see where this is coming from, but I still think it would be weird to import @typegpu/sort for something that is not a sorting algorihtm. I also think this is kind of limiting for other algorithms we might implement in the future.
How about @typegpu/compute-utils, @typegpu/array-algo?
I've googled that "primitive" could describe such algorithms, so maybe @typegpu/primitives?

[reczkok]

I would rather be too specific than too vague, both @typegpu/compute-utils and @typegpu/primitives could describe absolutely anything

[aleksanderkatan]

I think that the package name should always be wide enough to encompass every export. Cube marching also requires prefix scan, if there ever is a package for cube marching, should it export prefix scan as well?

[reczkok]

I think that logic doesn’t quite apply here. A package for marching cubes has a very specific, well-defined use case. Something like @typegpu/sort, on the other hand, describes a broader category of algorithms. In that context, including related primitives like prefix scan seems reasonable.

If this were a more narrowly scoped package, for example @typegpu/bitonic-sort, then I’d agree it shouldn’t export something like a prefix scan. But for a general @typegpu/sort package, that feels fair to me.

[iwoplaza]

After debating both internally and with external contributors, I think going with @typegpu/algorithm is the right way to go.