-
Notifications
You must be signed in to change notification settings - Fork 13.1k
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
Rename Piece::String
to Piece::Lit
#135943
Conversation
This comment has been minimized.
This comment has been minimized.
Please in the future indicate clearly when you're stacking changes from another PR, since this contains commits from #135882. |
@compiler-errors, sorry Michael, still figuring out how to best organize my workflow locally :) |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
rust-analyzer is developed in its own repository. If possible, consider making this change to rust-lang/rust-analyzer instead. cc @rust-lang/rust-analyzer |
Piece::String
to Piece::Lit
and make it easier to check "similar tokens"
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.
Ping me after #135882 lands and this PR gets rebased. r=me.
Piece::String
to Piece::Lit
and make it easier to check "similar tokens"Piece::String
to Piece::Lit
@estebank I figured out how to rebase this, so I think this is now reviewable. |
S2: Into<string::String>, | ||
S3: Into<string::String>, | ||
>( | ||
fn err_with_note<S1: Into<String>, S2: Into<String>, S3: Into<String>>( |
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.
This is not because of you, it's just a fmt change, but nowadays we'd likely have written these using impl Into<String>
.
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.
Fixed both here and just above for fn err
. And it was already merged so I probably messed up this PR now...
@bors r+ |
Rename `Piece::String` to `Piece::Lit` This renames Piece::String to Piece::Lit to avoid shadowing std::string::String and removes "pub use Piece::*;".
Rename `Piece::String` to `Piece::Lit` This renames Piece::String to Piece::Lit to avoid shadowing std::string::String and removes "pub use Piece::*;".
Rollup of 7 pull requests Successful merges: - rust-lang#135625 ([cfg_match] Document the use of expressions.) - rust-lang#135902 (Do not consider child bound assumptions for rigid alias) - rust-lang#135943 (Rename `Piece::String` to `Piece::Lit`) - rust-lang#136104 (Add mermaid graphs of NLL regions and SCCs to polonius MIR dump) - rust-lang#136143 (Update books) - rust-lang#136147 (ABI-required target features: warn when they are missing in base CPU) - rust-lang#136164 (Refactor FnKind variant to hold &Fn) r? `@ghost` `@rustbot` modify labels: rollup
Rollup merge of rust-lang#135943 - hkBst:opt_imports, r=estebank Rename `Piece::String` to `Piece::Lit` This renames Piece::String to Piece::Lit to avoid shadowing std::string::String and removes "pub use Piece::*;".
☔ The latest upstream changes (presumably #136225) made this pull request unmergeable. Please resolve the merge conflicts. |
Do not push after r+ (and when pr in rollup), this results in probably wrong commit state merged, and now merged in #136225. |
The main changes have effectively been merged by the rollup. Namely commit 3026545. The following post-r+ force-push was not included on master: https://github.com/rust-lang/rust/compare/3026545ab50e65fcd1c888b77272032000e36147..faa086152b7658f4ed1394b8d82b7055470b61c9. As [@]klensy wrote, please don't push after an r+ (unless overwritten by a subsequent r-). Closing as effectively merged. There's nothing else we could do (well, we could re-r+ this but that wouldn't be any less confusing for future GitHub archeologists; it'd better to open a new PR for any further modifications unless they're trivial) |
Sorry, this was a dumb mistake. New PR at #136251. I don't suppose there is anything I can do to fix things? |
Hmm, I haven't tried to recover from such a situation before (it's not strictly necessary to do so). I was about to say, please don't force-push to this branch and don't delete it and I'll see what I can do but I can actually no longer reopen this PR because you reused the branch for your new PR #136251 >.< GH won't let me ("There is already an open pull request from hkBst:opt_imports to rust-lang:master"). I would've probably tried to reset the branch to the old master used originally and cherry-picked the original commit but that could've made this even worse maybe (with GH possibly showing all commits in old_master..current_master in this PR or showing an "empty" diff, idk). In any case, don't let it trouble you. It's unfortunate but my hands are tied. |
This renames Piece::String to Piece::Lit to avoid shadowing std::string::String and removes "pub use Piece::*;".