Skip to content

Conversation

komyg
Copy link
Contributor

@komyg komyg commented Oct 4, 2025

No description provided.

@komyg komyg force-pushed the feature/promise.all_settled branch from 6271720 to 16237ab Compare October 11, 2025 11:10
pub(crate) realms: Vec<Option<RealmRecord<'static>>>,
pub(crate) promise_all_records: Vec<PromiseAllRecord<'static>>,
pub(crate) promise_all_settled_records: Vec<PromiseAllSettledRecord<'static>>,
pub(crate) promise_group_records: Vec<PromiseGroupRecord<'static>>,
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

issue: The intention behind the "PromiseGroup" is that PromiseAll and PromiseAllSettled would not exist as separate categories / vectors in the heap, but instead they'd both just be "PromiseGroups" of some kind, with the exact kind of the group determined by what the enum variant of the PromiseGroupRecord is.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, that is my intention.

I left the other records there, so that I could test my changes without a huge change, but I will remove them once the PromiseGroup is fully ready.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ah, roger, my bad!

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