-
Notifications
You must be signed in to change notification settings - Fork 117
RFC: Custom backends and policies for Dynamic Selection #2220
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
base: main
Are you sure you want to change the base?
Conversation
The `get_submission_group` is not easily implemented in a meaningful way. It must return a type that | ||
defines a member function `wait`. But since there is no way to know how to wait on all previous submissions | ||
for an arbitrary backend resource, this function will likely need to return a dummy type or | ||
`get_submission_group` be undefined for the default backend. |
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.
If we could provide a way to have the user give us the wait type, do we have a shot? Or maybe it's better to leave this out to make the default case simple.
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.
Lets consider if there's a meaningful default or not. I'm not sure that there is.
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.
I think a meaningful default is to call wait on all resources, if they have a wait function.
Co-authored-by: Dan Hoeflinger <[email protected]>
Co-authored-by: Dan Hoeflinger <[email protected]>
Co-authored-by: Dan Hoeflinger <[email protected]>
Co-authored-by: Dan Hoeflinger <[email protected]>
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.
I think this looks pretty good. Mostly just quite minor changes for now.
Co-authored-by: Dan Hoeflinger <[email protected]>
Co-authored-by: Dan Hoeflinger <[email protected]>
Co-authored-by: Dan Hoeflinger <[email protected]>
Co-authored-by: Dan Hoeflinger <[email protected]>
Co-authored-by: Dan Hoeflinger <[email protected]>
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.
first pass at feedback
rfcs/proposed/dynamic_selection_customization/custom_backends.md
Outdated
Show resolved
Hide resolved
rfcs/proposed/dynamic_selection_customization/custom_backends.md
Outdated
Show resolved
Hide resolved
rfcs/proposed/dynamic_selection_customization/custom_backends.md
Outdated
Show resolved
Hide resolved
rfcs/proposed/dynamic_selection_customization/custom_backends.md
Outdated
Show resolved
Hide resolved
rfcs/proposed/dynamic_selection_customization/custom_backends.md
Outdated
Show resolved
Hide resolved
rfcs/proposed/dynamic_selection_customization/custom_policies.md
Outdated
Show resolved
Hide resolved
rfcs/proposed/dynamic_selection_customization/custom_backends.md
Outdated
Show resolved
Hide resolved
rfcs/proposed/dynamic_selection_customization/custom_backends.md
Outdated
Show resolved
Hide resolved
rfcs/proposed/dynamic_selection_customization/custom_backends.md
Outdated
Show resolved
Hide resolved
rfcs/proposed/dynamic_selection_customization/custom_backends.md
Outdated
Show resolved
Hide resolved
rfcs/proposed/dynamic_selection_customization/custom_backends.md
Outdated
Show resolved
Hide resolved
Signed-off-by: Dan Hoeflinger <[email protected]>
Signed-off-by: Dan Hoeflinger <[email protected]>
Signed-off-by: Dan Hoeflinger <[email protected]>
Signed-off-by: Dan Hoeflinger <[email protected]>
Signed-off-by: Dan Hoeflinger <[email protected]>
Signed-off-by: Dan Hoeflinger <[email protected]>
A very rough draft for custom backends for dynamic selection.