Skip to content

Implement Future aggregation functions.#1981

Merged
player-03 merged 1 commit intoopenfl:9.0.0-devfrom
player-03:Future_aggregation_functions
Feb 4, 2026
Merged

Implement Future aggregation functions.#1981
player-03 merged 1 commit intoopenfl:9.0.0-devfrom
player-03:Future_aggregation_functions

Conversation

@player-03
Copy link
Contributor

These are based on JavaScript's promise concurrency functions, using Lime's nomenclature.

Supersedes #1844

@player-03
Copy link
Contributor Author

@EliteMasterEric How do these look to you?

@player-03
Copy link
Contributor Author

I'm going back and forth between calling it "allResolved" or "allSettled".

  • Lime's Promise class consistently uses the term "resolve".
  • We're copying JavaScript's functions, so it'd be more intuitive to use JavaScript's names.
  • The function works slightly differently than the JS version, so maybe a slightly different name will make the change more obvious.
  • Wikipedia uses the term "resolve".

@EliteMasterEric
Copy link
Contributor

Just saw the notification for this.

I'm happy with this implementation. I think resolve makes the most sense considering the rest of the codebase uses that terminology.

@player-03 player-03 merged commit bab7caf into openfl:9.0.0-dev Feb 4, 2026
27 checks passed
@player-03 player-03 deleted the Future_aggregation_functions branch February 4, 2026 18:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants