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) --- ops/optimizer.rs | 30 ++++++++++++++++++++++-------- 1 file changed, 22 insertions(+), 8 deletions(-) (limited to 'ops/optimizer.rs') diff --git a/ops/optimizer.rs b/ops/optimizer.rs index 3f22a867b..1a6172b67 100644 --- a/ops/optimizer.rs +++ b/ops/optimizer.rs @@ -5,15 +5,28 @@ use std::collections::BTreeMap; use std::fmt::Debug; use std::fmt::Formatter; -use pmutil::{q, Quote}; +use pmutil::q; +use pmutil::Quote; use proc_macro2::TokenStream; -use syn::{ - parse_quote, punctuated::Punctuated, token::Colon2, - AngleBracketedGenericArguments, FnArg, GenericArgument, PatType, Path, - PathArguments, PathSegment, ReturnType, Signature, Type, TypePath, TypePtr, - TypeReference, TypeSlice, TypeTuple, -}; +use syn::parse_quote; +use syn::punctuated::Punctuated; +use syn::token::Colon2; +use syn::AngleBracketedGenericArguments; +use syn::FnArg; +use syn::GenericArgument; +use syn::PatType; +use syn::Path; +use syn::PathArguments; +use syn::PathSegment; +use syn::ReturnType; +use syn::Signature; +use syn::Type; +use syn::TypePath; +use syn::TypePtr; +use syn::TypeReference; +use syn::TypeSlice; +use syn::TypeTuple; use crate::Op; @@ -678,7 +691,8 @@ fn double_segment( #[cfg(test)] mod tests { use super::*; - use crate::{Attributes, Op}; + use crate::Attributes; + use crate::Op; use std::path::PathBuf; use syn::parse_quote; -- cgit v1.2.3