-
Notifications
You must be signed in to change notification settings - Fork 482
Add more solid and generic process wrapper #372
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
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Overall I don't see any blockers, however if you don't mind, could we add a bit more explanation to errors and let @epigramengineer test this one?
Co-authored-by: Damien Martin-Guillerez <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As it passes all the test, I am fine with this PR, I am going to wait another day for @epigramengineer to chime in on #375 before merging this one.
So tried from a clean Linux VM to make sure that everything in a minimalist project work. And it seems to be fine, not that it worked also without this PR. |
Ok we are one day later, so let's merge this one. |
The new process wrapper is in the process of being reviewed so it can be part of the skylib, in the meantime, some work have been invested in making it more solid, and some functionality like capturing the std output of the child process have been added.
This will allow us to use it to call rustfmt.