-
Notifications
You must be signed in to change notification settings - Fork 210
refactor: imports #600
New issue
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
base: master
Are you sure you want to change the base?
refactor: imports #600
Conversation
Apparently, this code has been worked on for a very long time. This means that some things within the code are outdated. These things have been modernised.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks like a few cargo fmt
lints to fix
Why does the |
Have you considered upgrading your toolchain to the most recent version? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is that good?
Getting to this now, sorry for the delay. Can I ask what you ran to format the imports? |
Therefore I add the following entry to imports_granularity = "Crate" this is a nightly feature, so I did not add it to the pull request. |
Hmm. I see the following potential issue: if someone is working on stable and adds or changes an import, there isn't a guarantee that those changes will have a consistent style because 1) the |
I can also add the entry to |
Imported dependencies must be formatted!