Skip to content
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

Add destroyForcibly to scala.sys.process.Process #10106

Open
scabug opened this issue Dec 13, 2016 · 5 comments
Open

Add destroyForcibly to scala.sys.process.Process #10106

scabug opened this issue Dec 13, 2016 · 5 comments

Comments

@scabug
Copy link

scabug commented Dec 13, 2016

Since Java 8, java.lang.Process has a new method — destroyForcibly(...). On some platforms it actually kills a process. It would be nice to have it in scala.sys.process.Process as well.

@scabug
Copy link
Author

scabug commented Dec 13, 2016

Imported From: https://issues.scala-lang.org/browse/SI-10106?orig=1
Reporter: Alex Zolotko (azolotko)
Affected Versions: 2.12.1
See #9454

@scabug
Copy link
Author

scabug commented Dec 14, 2016

@som-snytt said:
There's also waitFor with a duration. Might be occasion to settle how to incorporate API creep.

@scabug
Copy link
Author

scabug commented Dec 14, 2016

@SethTisue said:
sys.process seems like a prime candidate for being spun off as a module...

@som-snytt
Copy link

To follow up my previous comment, is this meaningful in the context of lots of I/O threads and Process implementations like ThreadProcess?

It makes more sense to expose the underlying Java Process, perhaps as an Option[Process] since not all Scala Process have an underlying one.

@SethTisue
Copy link
Member

@MrRexZ need your thoughts on Som's response before we could merge the PR.

also, for discussion purposes, it might be helpful to understand if you were just looking around in scala/bug for something to help with? or, is this an addition you really want?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants