-
Notifications
You must be signed in to change notification settings - Fork 7
✨ [parallelisation] Extend the cancel/close store to have various ways of functioning (e.g. parallel, sequential, reverse order, etc.)
#676
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
…ays of functioning (e.g. parallel, sequential, reverse order, etc.)
| option := ExecuteAll | ||
| if stopOnFirstError { | ||
| option = StopOnFirstError | ||
| } |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Having an option only represent a positive will help us avoid overwriting options which will simplify option interactions if things get complicated, what do you think?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
the overwriting is because the stores cancel and close have fundamentally different behaviours
| } | ||
| } | ||
|
|
||
| // NewCloseFunctionStoreStore is exactly the same as NewConcurrentCloseFunctionStore but without a typo in the name. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
what typo ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
StoreStore in the name
Co-authored-by: Abdelrahman Abdelraouf <abdelrahman.abdelraouf@arm.com>
Description
Extend the stores so it can be executed differently : i.e. sequentially vs concurrently
Test Coverage