summaryrefslogtreecommitdiff
path: root/ext/web/message_port.rs
diff options
context:
space:
mode:
authorDivy Srivastava <dj.srivastava23@gmail.com>2023-01-14 20:18:58 -0800
committerGitHub <noreply@github.com>2023-01-14 23:18:58 -0500
commitd5634164cb86771fc279468cbb93e311c1ad3089 (patch)
tree2878a536acdb5106e48488e640cd78dfa2b5893a /ext/web/message_port.rs
parentefcbfd5206fcdfac55c26a7133c04dd330d047b9 (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 'ext/web/message_port.rs')
-rw-r--r--ext/web/message_port.rs9
1 files changed, 6 insertions, 3 deletions
diff --git a/ext/web/message_port.rs b/ext/web/message_port.rs
index f287fc82d..47ebdabf7 100644
--- a/ext/web/message_port.rs
+++ b/ext/web/message_port.rs
@@ -8,10 +8,13 @@ use deno_core::error::type_error;
use deno_core::error::AnyError;
use deno_core::op;
+use deno_core::CancelFuture;
+use deno_core::CancelHandle;
use deno_core::DetachedBuffer;
-use deno_core::{CancelFuture, Resource};
-use deno_core::{CancelHandle, OpState};
-use deno_core::{RcRef, ResourceId};
+use deno_core::OpState;
+use deno_core::RcRef;
+use deno_core::Resource;
+use deno_core::ResourceId;
use serde::Deserialize;
use serde::Serialize;
use tokio::sync::mpsc::unbounded_channel;