Allow CI Workflow Run

• approve CI run for commit: 13cb931

Note: this should only be enabled once the PR is ready to go and can only be enabled by a maintainer

Allow CI Workflow Run

• approve CI run for commit: 49dc633

Note: this should only be enabled once the PR is ready to go and can only be enabled by a maintainer

Hi,

This is one of those topics where it is fairly easy to talk past each other. Let me first value the PR, there are good ideas here, I’ll add some review comments so we can land it.

The root problem as I see it, is the placement of the comments and how the section hints at Promise.all as the executor, when in reality it is just a collector.

Whether operations run in parallel is a function of the host environment, not of Promise APIs. For example, when you call fetch twice, the network stack (browser or Node/undici) can issue both requests in parallel, but JavaScript itself remains single‑threaded.

const a = fetch('/a'); // request is initiated here
const b = fetch('/b'); // and here
await Promise.all([a, b]); // this only awaits both

For CPU-bound work, there's no such thing as parallelism without Worker Threads/Web Workers - and at best async/tasks just interleave, so that operations look concurrent.

I'll leave some comments, let's discuss over those and try to land some changes :)

Thanks, I added your suggestions, pls take a look when you have the chance.