summaryrefslogtreecommitdiff
path: root/cli/napi/sym/README.md
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 /cli/napi/sym/README.md
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 'cli/napi/sym/README.md')
-rw-r--r--cli/napi/sym/README.md5
1 files changed, 4 insertions, 1 deletions
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(