-
Notifications
You must be signed in to change notification settings - Fork 13k
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
rustfmt librustc_resolve #34584
rustfmt librustc_resolve #34584
Conversation
r? @pnkfelix (rust_highfive has picked a reviewer for you, use r? to override) |
cc @jseyfried, most of this formatting is yours. |
@petrochenkov what does "most of this formatting is yours" mean? |
@tshepang |
@which parts of the diff do you not like? |
kind: NameBindingKind::Module(self.0), | ||
span: self.1, | ||
vis: self.2, | ||
} |
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.
Struct expression fits into one line but splitted into several lines anyway (1).
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.
I find this more readable
Ok, that's enough for now. |
@petrochenkov You summed up my thoughts on these PRs exactly :) Also, "visual indenting" of function calls with many arguments really bothers me: let foo = some_long_function_name("a reasonable string literal",
another_argument,
a,
b,
c,
x,
y); This often causes really bad rightward drift, really bad diffs, wasted vertical space, and general ugliness. I'd much prefer let foo = some_long_function_name(
"a relatively short string literal", another_argument, a, b, c, x, y,
); |
☔ The latest upstream changes (presumably #34365) made this pull request unmergeable. Please resolve the merge conflicts. |
highly-opposed and too many merge conflicts |
No description provided.