Closed rauhul closed 3 months ago
If you insist on moving it out of Basics
, it could be kept in Basics
here as a stopgap measure. After AsyncProcess
PR is merged, Environment
could be moved to that new AsyncProcess
module.
It seems like AsyncProcess
module is indeed a good place for this type.
Main problem with that is a dependency on AbsolutePath
in the AsyncProcess
type itself. For the sake of not opening that can of modularization worms, I'd prefer this PR to be focused on fixing the actual warnings only. We can come back to modularization issues separately. This would also make PRs smaller and easier to review.
@swift-ci test
@swift-ci test windows
@compnerd would you have a moment to look how well this works for Windows compatibility?
@swift-ci test windows
@swift-ci test
@swift-ci test windows
@swift-ci test windows
looks like windows CI is failing to checkout Swift which is odd because the other checks are working
@swift-ci test windows
@swift-ci test windows
@swift-ci test
@swift-ci test windows
Adds a new
Environment
type to replace TSCBasics EnvironmentVariables and ProcessEnvironmentBlock types. Updates points of use of the older APIs with the newer API and adds unit tests forEnvironment
.