-
Notifications
You must be signed in to change notification settings - Fork 38
Subprocess pipelines #176
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
Open
cmcgee1024
wants to merge
57
commits into
swiftlang:main
Choose a base branch
from
cmcgee1024:pipe
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Subprocess pipelines #176
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Create complex pipeline stages and run the pipeline configuration using a single I/O configuration based on the usual Input, Output, and Error options provided by the existing run() functions. Each stage can be either a process or a Swift function. For processes there are the typical executable, arguments, or configuration parameters. There is an additional process option to rewire standard output and standard error in typical ways, such as merging the two to standard output, or replacing standard output with standard error. A Swift function stage can read from its input, and write to its output/error streams much like a process, but provides the full Swift power in the current process to parse JSON and do other powerful things. Similarly, an exit code can be returned. Provide a rich set of top-level functions, methods and overloaded operators to construct and execute the pipelines.
…for either Unix or Windows
…e with CreateIoCompletionPort
… between test outcomes on different platforms
The macOS build error seems unrelated to the changes here. It's failing on an ambiguous Region type. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Create complex pipeline stages and run the pipeline configuration using a single I/O configuration based on the usual Input, Output, and Error options provided by the existing run() functions.
Each stage can be either a process or a Swift function. For processes there are the typical executable, arguments, or configuration parameters. There is an additional process option to rewire standard output and standard error in typical ways, such as merging the two to standard output, or replacing standard output with standard error.
A Swift function stage can read from its input, and write to its output/error streams much like a process, but provides the full Swift power in the current process to parse JSON and do other powerful things. Similarly, an exit code can be returned.
Provide a rich set of top-level functions, methods and overloaded operators to construct and execute the pipelines.