Skip to content

Making Execution ~Copyable instead of class #2

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.

Sign up for GitHub

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

Jump to bottom
Closed
iCharlesHu opened this issue Apr 7, 2025 · 0 comments · Fixed by #38
Closed

Making Execution ~Copyable instead of class #2

iCharlesHu opened this issue Apr 7, 2025 · 0 comments · Fixed by #38
Assignees
@iCharlesHu
Labels
blocker Show stopping issues for 0.0.1

Comments

@iCharlesHu
Copy link
Contributor

Execution semantically should be ~Copyable because it represents an instance of a process that has already executed. We ran into issues marking it ~Copyable because we have to capture output and error concurrently, thus through different contexts. We should re-explore making Execution ~Copyable
@iCharlesHu iCharlesHu self-assigned this Apr 7, 2025
@iCharlesHu iCharlesHu mentioned this issue May 9, 2025
Merged
@iCharlesHu iCharlesHu added the blocker Show stopping issues for 0.0.1 label May 16, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@iCharlesHu iCharlesHu

Labels
blocker Show stopping issues for 0.0.1
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Adopt ~Copyable in Subprocess iCharlesHu/swift-subprocess
1 participant
@iCharlesHu