Swift Async Algorithms 1.1 Planning

[vanvoorden (Rick van Voorden)]

@ph1ps

Besides that, is splitting up the algorithms into submodules something that was considered? swift-collections has this, although swift-algorithms does not, so there is no preferred way I guess. But I mostly only use 1-2 algorithms when I depend on AsyncAlgorithms myself.

I believe the solution being considered is package traits:

@FranzBusch

@vanvoorden

Maybe this is more of a feedback for the diff review… but do we know what kind of horizontal dependencies we expect between share and the rest of the package? Could this potentially ship in a "subpackage" target under AsyncAlgorithms so that a product engineer that needs only share could link just against that code and not pay a binary size and compile time penalty for code they might not need?

This has come up before and we could leverage package traits to move each algorithm behind a trait and enable all by default. This would allow other packages to only pick the algorithms they need.