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 /core/modules.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 'core/modules.rs')
| -rw-r--r-- | core/modules.rs | 3 |
1 files changed, 2 insertions, 1 deletions
diff --git a/core/modules.rs b/core/modules.rs index 917649c85..8a79143f0 100644 --- a/core/modules.rs +++ b/core/modules.rs @@ -1190,7 +1190,8 @@ mod tests { use std::future::Future; use std::io; use std::path::PathBuf; - use std::sync::atomic::{AtomicUsize, Ordering}; + use std::sync::atomic::AtomicUsize; + use std::sync::atomic::Ordering; use std::sync::Arc; // deno_ops macros generate code assuming deno_core in scope. mod deno_core { |