diff options
| author | bors <bors@rust-lang.org> | 2013-12-14 12:56:22 -0800 |
|---|---|---|
| committer | bors <bors@rust-lang.org> | 2013-12-14 12:56:22 -0800 |
| commit | aafed3ece58be56e5e88c51d32d065254f10309a (patch) | |
| tree | 21d55824a8a38d055f478c1abf5c962787113c87 /src/rustllvm/RustWrapper.cpp | |
| parent | 3d3a663d2530dd49fee235667e98f2767dfd1b57 (diff) | |
| parent | 5de42701a87cb0e517921cce7bc3a512e513301c (diff) | |
| download | rust-aafed3ece58be56e5e88c51d32d065254f10309a.tar.gz rust-aafed3ece58be56e5e88c51d32d065254f10309a.zip | |
auto merge of #10936 : cadencemarseille/rust/issue-10754-std-run-unwrap-on-None, r=alexcrichton
The problem was that std::run::Process::new() was unwrap()ing the result of std::io::process::Process::new(), which returns None in the case where the io_error condition is raised to signal failure to start the process. Have std::run::Process::new() similarly return an Option\<run::Process\> to reflect the fact that a subprocess might have failed to start. Update utility functions run::process_status() and run::process_output() to return Option\<ProcessExit\> and Option\<ProcessOutput\>, respectively. Various parts of librustc and librustpkg needed to be updated to reflect these API changes. closes #10754
Diffstat (limited to 'src/rustllvm/RustWrapper.cpp')
0 files changed, 0 insertions, 0 deletions
