From d5634164cb86771fc279468cbb93e311c1ad3089 Mon Sep 17 00:00:00 2001 From: Divy Srivastava Date: Sat, 14 Jan 2023 20:18:58 -0800 Subject: 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) --- cli/napi/sym/README.md | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) (limited to 'cli/napi') diff --git a/cli/napi/sym/README.md b/cli/napi/sym/README.md index b3e2ab43b..de08a8e17 100644 --- a/cli/napi/sym/README.md +++ b/cli/napi/sym/README.md @@ -8,7 +8,10 @@ A proc_macro for Deno's Node-API implementation. It does the following things: - Maps `deno_napi::Result` to raw `napi_result`. ```rust -use deno_napi::{napi_value, Env, Error, Result}; +use deno_napi::napi_value; +use deno_napi::Env; +use deno_napi::Error; +use deno_napi::Result; #[napi_sym::napi_sym] fn napi_get_boolean( -- cgit v1.2.3