-
Notifications
You must be signed in to change notification settings - Fork 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.
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
Consider using process::ExitCode
, and driving its design too
#1
Comments
Hey, thanks for the comment. I was aware of Is there a way to extend |
Thinks like "gee, this should have a way to do more than success/failure" are exactly the kind of design work that the type needs 🙂 For example, people have suggested providing constants for the BSD Certainly making them from integers is also logical. It's non-obvious if it should always support And who knows, maybe the Plan9 implementation should even make them from strings (http://man.cat-v.org/plan_9/2/exits). |
There's the unstable
std::process::ExitCode
(tracking issue rust-lang/rust#48711) that also has aTermination
impl: https://doc.rust-lang.org/nightly/std/process/struct.ExitCode.html#impl-TerminationIt never had an RFC, so it needs someone to figure out what it should look like and how it should be used. Since you're looking at related things, maybe its worth experimenting with here?
It might be useful to have things define
Into<ExitCode>
instead ofInto<i32>
; I don't know.The text was updated successfully, but these errors were encountered: