Skip to content
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

run rustfmt on librustc_passes folder #33951

Merged
merged 1 commit into from
Aug 6, 2016
Merged

run rustfmt on librustc_passes folder #33951

merged 1 commit into from
Aug 6, 2016

Conversation

srinivasreddy
Copy link
Contributor

No description provided.

@rust-highfive
Copy link
Collaborator

r? @nikomatsakis

(rust_highfive has picked a reviewer for you, use r? to override)

self.tcx.sess.add_lint(CONST_ERR,
expr.id,
expr.span,
format!("constant evaluation error: {}. This will \
become a HARD ERROR in the future",
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Becomes weirdly misaligned.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I didn't find an existing rustfmt issue, so I filed rust-lang/rustfmt#1026 -- @nagisa, is that what you meant?

@nikomatsakis
Copy link
Contributor

I'd be happy to r+ but for this tidy failure:

https://travis-ci.org/rust-lang/rust/builds/133743527#L1234

seems like a bug in rustfmt?

@srinivasreddy
Copy link
Contributor Author

@nikomatsakis I roll up please. I removed that line manually.

@nikomatsakis
Copy link
Contributor

@srinivasreddy did you file some sort of bug in rustfmt repo?

@srinivasreddy
Copy link
Contributor Author

nope.AFAIK, Not required. rustfmt does not panic when it crosses 100 chars limit in a line and goes on formatting, And it just gives you sorry message on console. I guess it is an expected behaviour. Let's confirm with what @nrc says.

@nikomatsakis
Copy link
Contributor

@srinivasreddy seems like this bug rust-lang/rustfmt#1080 fits the bill, sort of.

@nikomatsakis
Copy link
Contributor

@bors r+ rollup

@bors
Copy link
Contributor

bors commented Jun 27, 2016

📌 Commit faa039f has been approved by nikomatsakis

steveklabnik added a commit to steveklabnik/rust that referenced this pull request Jun 27, 2016
… r=nikomatsakis

run rustfmt on librustc_passes folder
@bors
Copy link
Contributor

bors commented Jun 28, 2016

☔ The latest upstream changes (presumably #34424) made this pull request unmergeable. Please resolve the merge conflicts.

bors added a commit that referenced this pull request Jun 28, 2016
@bors
Copy link
Contributor

bors commented Jul 1, 2016

🔒 Merge conflict

bors added a commit that referenced this pull request Jul 7, 2016
bors added a commit that referenced this pull request Jul 12, 2016
Rollup of 7 pull requests

- Successful merges: #34736, #34737, #34740, #34742, #34749, #34750, #34770
- Failed merges: #33951
bors added a commit that referenced this pull request Jul 15, 2016
Rollup of 7 pull requests

- Successful merges: #34456, #34733, #34777, #34794, #34799, #34804, #34818
- Failed merges: #33951
are not allowed, use unit structs and \
enum variants instead")
.span_help(span, "remove trailing `()` to make a unit \
.span_help(span,
"remove trailing `()` to make a unit \
struct or unit enum variant")
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Strange indent.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

All of these are due to the same reason and all should be fixed up manually.

@bors
Copy link
Contributor

bors commented Jul 28, 2016

☔ The latest upstream changes (presumably #34907) made this pull request unmergeable. Please resolve the merge conflicts.

@nikomatsakis
Copy link
Contributor

Just in general my feeling is that if there is "suboptimal" formatting we should certainly make issues about it and discuss it as rustfmt guidelines get hammered out, but in general we want to adopt automated formatting just because it everyone's life easier -- even if there are some corner cases where hand-formatting might improve things. (Most of the examples raised here I personally could go either way, I admit.)

@nikomatsakis
Copy link
Contributor

@srinivasreddy want to rebase this?

@srinivasreddy
Copy link
Contributor Author

@nikomatsakis Done.

@bors
Copy link
Contributor

bors commented Aug 4, 2016

☔ The latest upstream changes (presumably #35015) made this pull request unmergeable. Please resolve the merge conflicts.

@srinivasreddy
Copy link
Contributor Author

@nikomatsakis Done.

@nikomatsakis
Copy link
Contributor

@bors r+

@bors
Copy link
Contributor

bors commented Aug 5, 2016

📌 Commit a6c9404 has been approved by nikomatsakis

@bors
Copy link
Contributor

bors commented Aug 6, 2016

⌛ Testing commit a6c9404 with merge 1fd8b88...

bors added a commit that referenced this pull request Aug 6, 2016
…akis

run rustfmt on librustc_passes folder
eddyb added a commit to eddyb/rust that referenced this pull request Aug 6, 2016
… r=nikomatsakis

run rustfmt on librustc_passes folder
@bors
Copy link
Contributor

bors commented Aug 6, 2016

⛄ The build was interrupted to prioritize another pull request.

bors added a commit that referenced this pull request Aug 6, 2016
@bors
Copy link
Contributor

bors commented Aug 6, 2016

⛄ The build was interrupted to prioritize another pull request.

@bors bors merged commit a6c9404 into rust-lang:master Aug 6, 2016
@srinivasreddy srinivasreddy deleted the librust_pass_rustfmt branch August 7, 2016 04:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants