Allow custom runtimes to use Executor #2285
Merged
+16
−0
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.
Hello folks! This PR makes a small change to
Executor
to allow it be used for custom runtimes. The only downside I can see is that the currentNotSupportedException
is probably a useful reminder when adding built-in runtimes, to ensure the correct behaviour is added or re-used here.My use-case: I've written a custom runtime, and currently I need to copy/paste all of
Executor
and its supporting classes into my own codebase, which seems a bit redundant when all I really want to change are these 3 lines. Of course this particular setup forProcessStartInfo
is not applicable for every custom runtime - but at least it allowsExecutor
to be used for those runtimes for which this is applicable.But of course you'll have a better view of whether this change is a good idea and / or acceptable.