diff options
| author | Divy Srivastava <dj.srivastava23@gmail.com> | 2023-01-14 20:18:58 -0800 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2023-01-14 23:18:58 -0500 |
| commit | d5634164cb86771fc279468cbb93e311c1ad3089 (patch) | |
| tree | 2878a536acdb5106e48488e640cd78dfa2b5893a /runtime/ops/runtime.rs | |
| parent | efcbfd5206fcdfac55c26a7133c04dd330d047b9 (diff) | |
chore: use rustfmt imports_granularity option (#17421)
Closes https://github.com/denoland/deno/issues/2699
Closes https://github.com/denoland/deno/issues/2347
Uses unstable rustfmt features. Since dprint invokes `rustfmt` we do not
need to switch the cargo toolchain to nightly. Do we care about
formatting stability of our codebase across Rust versions? (I don't)
Diffstat (limited to 'runtime/ops/runtime.rs')
| -rw-r--r-- | runtime/ops/runtime.rs | 12 |
1 files changed, 7 insertions, 5 deletions
diff --git a/runtime/ops/runtime.rs b/runtime/ops/runtime.rs index b97741acc..70814e3b8 100644 --- a/runtime/ops/runtime.rs +++ b/runtime/ops/runtime.rs @@ -44,12 +44,14 @@ pub fn ppid() -> i64 { // - MIT license use std::mem; use winapi::shared::minwindef::DWORD; - use winapi::um::handleapi::{CloseHandle, INVALID_HANDLE_VALUE}; + use winapi::um::handleapi::CloseHandle; + use winapi::um::handleapi::INVALID_HANDLE_VALUE; use winapi::um::processthreadsapi::GetCurrentProcessId; - use winapi::um::tlhelp32::{ - CreateToolhelp32Snapshot, Process32First, Process32Next, PROCESSENTRY32, - TH32CS_SNAPPROCESS, - }; + use winapi::um::tlhelp32::CreateToolhelp32Snapshot; + use winapi::um::tlhelp32::Process32First; + use winapi::um::tlhelp32::Process32Next; + use winapi::um::tlhelp32::PROCESSENTRY32; + use winapi::um::tlhelp32::TH32CS_SNAPPROCESS; // SAFETY: winapi calls unsafe { // Take a snapshot of system processes, one of which is ours |