-
Notifications
You must be signed in to change notification settings - Fork 909
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
docs: clarify the editions behavior and it's consequences on formatting #6486
Conversation
7b9fba8
to
aa2f3ec
Compare
Okay, I think I addressed everything, let me know if there is anything else to tweak. |
3085143
to
21852b6
Compare
I fixed those 2 issues you had and I fast-forwarded the branch. |
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.
Thanks so much for the edits. Please see my suggestions for additional updates to the docs.
Co-authored-by: Yacin Tmimi <[email protected]>
57e11a7
to
ecf3b62
Compare
afab171
to
4f89165
Compare
If you have no further suggestions, should I squash the changes into a single commit? |
If you'd like, but I can squash and merge too if that's easier. |
I could do it, but I'm not sure on the semantics of the squashed commit (the name and description), so if you can do it, go ahead. |
When using
rustfmt
directly on a project targeting the 2024 edition, the formatting differs fromcargo fmt
becauserustfmt
defaults to the 2015 edition. This discrepancy causes inconsistencies, especially when tools like editors automatically runrustfmt
on save, leading to files being reformatted to the 2015 edition style.I tried to explain this behavior concisely in the docs.
Fixes #6483.