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

Rustup with git subtree #5608

Merged
merged 14 commits into from
May 17, 2020
Merged

Rustup with git subtree #5608

merged 14 commits into from
May 17, 2020

Conversation

flip1995
Copy link
Member

The commits from the last rustup #5587, are again included in this rustup, since I rebased the rustup. Lesson learned: never rebase, only merge when working with git subtree.

changelog: none

ecstatic-morse and others added 13 commits May 3, 2020 11:41
Remove ast::{Ident, Name} reexports.

The reexport of `Symbol` into `Name` confused me.
Suggest to await future before ? operator

Closes rust-lang/rust#71811
cc #61076
rustc_driver: factor out computing the exit code

In a recent Miri PR I [added a convenience wrapper](https://github.com/rust-lang/miri/pull/1405/files#diff-c3d602c5c8035a16699ce9c015bfeceaR125) around `catch_fatal_errors` and `run_compiler` that @oli-obk suggested I could upstream. However, after seeing what could be shared between `rustc_driver::main`, clippy and Miri, really the only thing I found is computing the exit code -- so that's what this PR does.

What prevents using the Miri convenience function in `rustc_driver::main` and clippy is that they do extra work inside `catch_fatal_errors`, and while I could abstract that away, clippy actually *computes the callbacks* inside there, and I fond no good way to abstract that and thus gave up. Maybe the clippy thing could be moved out, I am not sure if it ever can actually raise a `FatalErrorMarker` -- someone more knowledgeable in clippy would have to do that.
…_cleanup, r=petrochenkov

Literal error reporting cleanup

While doing some performance work, I noticed some code duplication in `librustc_parser/lexer/mod.rs`, so I cleaned it up.

This PR is probably best reviewed commit by commit.

I'm not sure what the API stability practices for `librustc_lexer` are. Four public methods in `unescape.rs` can be removed, but two are used by clippy, so I left them in for now.
I could open a PR for Rust-Analyzer when this one lands.

But how do I open a PR for clippy? (Git submodules are frustrating to work with)
Maybe someday, git subtree will do it right
@flip1995 flip1995 requested a review from phansch May 16, 2020 23:39
@phansch
Copy link
Member

phansch commented May 17, 2020

@bors r+

@bors
Copy link
Contributor

bors commented May 17, 2020

📌 Commit 7f317b7 has been approved by phansch

@bors
Copy link
Contributor

bors commented May 17, 2020

⌛ Testing commit 7f317b7 with merge 440a46d...

@bors
Copy link
Contributor

bors commented May 17, 2020

☀️ Test successful - checks-action_dev_test, checks-action_remark_test, checks-action_test
Approved by: phansch
Pushing 440a46d to master...

@bors bors merged commit 440a46d into rust-lang:master May 17, 2020
@flip1995 flip1995 deleted the rustup branch May 17, 2020 15:27
bors added a commit to rust-lang-ci/rust that referenced this pull request May 18, 2020
Sync Clippy

cc rust-lang/rust-clippy#5608

Included changes:

- renames/merges of some lints
- ICE fix
- Downgrade useless_let_if_seq to nursery
- FP fixes
- formatting

r? @oli-obk
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.

10 participants