refactor: use standardized swift-async-algorithms

[Austinpayne]

Adopts the more common (now-a-days) swift-async-algorithms for the simple async collection needs of this package. Helps adopt the standardized ecosystem where many other packages use swift-async-algorithms.

[Austinpayne]

@NeedleInAJayStack

[NeedleInAJayStack]

I believe if you change this line from v3 to v4, that will resolve the 'Test on Linux' check:

DataLoader/.github/workflows/build.yml

Line 54 in 52b1f3d

uses: actions/upload-artifact@v3

[NeedleInAJayStack]

Looks great, thanks @Austinpayne

[paulofaria]

LGTM! Thank you for your contribution! 🙂

[Austinpayne]

I believe if you change this line from v3 to v4, that will resolve the 'Test on Linux' check:

DataLoader/.github/workflows/build.yml

Line 54 in 52b1f3d

uses: actions/upload-artifact@v3

Sweet, thanks! Pushed up a change to upgrade to v4.

[ZirgVoice]

You replaced concurrentMap, which works in parallel and can process all values in the array simultaneously, with map, which processes values sequentially. This will reduce the performance of the DataLoader.

[Austinpayne]

Yeah, it's true the semantics are different. Feel free to close if this potential performance change is unacceptable. I don't see any benchmarks in this package so I don't have a good way to qualify this change.

[NeedleInAJayStack]

I'm inclined to agree with @ZirgVoice. Batching works by slightly pausing execution to allow more load calls to get into the DataLoader's queue. This works because queue.append happens before any awaited operation, so concurrent load or loadManys can be combined. If instead we await on each load of a loadMany call, then those loads will not actually be batched to the backend.

I'm realizing that we ought to add a test that validates this functionality for loadMany though..

[Austinpayne]

Sounds good, thanks for the feedback!