When setting a limit with ->limit(X), it starts X futures initially, but falls back to doing one at a time for the rest of the futures. This is noticeable when running a linter or unit test engine that makes use of multiple futures as has a limit applied.
Description
Description
Revisions and Commits
Revisions and Commits
Related Objects
Related Objects
Event Timeline
Comment Actions
Re-reading D9115, I think I was never able to understand or reproduce this and it was ultimately mooted anyway.
Happy to look at this again if there's a modern repo / use case, but I don't think there's any way for this incarnation of it to move forward.