We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
I read in the book that mod statements like
use a::b; use a::c; use a::d::e; use a::d::f;
Can be reformatted with nested paths like
use a::{ b, c, d::{e, f}, };
What's a consensus about the right way to go? Is it in the scope of rustfmt to automatically handle this? If yes, how to configure rustfmt so it does?
rustfmt
The text was updated successfully, but these errors were encountered:
merge_imports (https://github.com/rust-lang/rustfmt/blob/master/Configurations.md).
merge_imports
Sorry, something went wrong.
@cynecx Thanks, so merge is the keyword I was missing instead of nest ;)
merge
nest
I read that the default value for this option is false, because the feature is not stabilized yet. See #3362 for discussion about it.
false
No branches or pull requests
I read in the book that mod statements like
Can be reformatted with nested paths like
What's a consensus about the right way to go?
Is it in the scope of
rustfmt
to automatically handle this?If yes, how to configure
rustfmt
so it does?The text was updated successfully, but these errors were encountered: