ExtensionPolicy changes required for Python callback support. #12417
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Should be merged after #12416, will rebase if there are any changes there. Creating as draft for now.
This PR changes the validator callback types to allow storing python callbacks in them.
The callback types have to be
Send
andSync
to allow theExtensionPolicy
to be stored inside aPyExtensionPolicy
pyclass. They areArc
to be able to clone theExtensionPolicy
, which is required for the builder-style API ofPyExtensionPolicy
.Hopefully this makes sense on it's own. I was originally going to include this as part of a larger PR adding all the functionality required to expose extension policies to python, but that was getting too big.