-
Notifications
You must be signed in to change notification settings - Fork 12.5k
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
Remove leftover chalk types #71758
Remove leftover chalk types #71758
Conversation
✌️ @jackh725 can now approve this pull request |
@nikomatsakis Are the error changes okay? Do you know why they changed? (also you delegated to wrong user) |
lol, so I did @bors delegate=jackh726 |
✌️ @jackh726 can now approve this pull request |
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.
It's true, I don't know what's causing the errors -- skimming the diff, I only found one thing that might be a problem.
Indeed, setting |
@bors r+ |
📌 Commit ef0da3b has been approved by |
Rollup of 5 pull requests Successful merges: - rust-lang#71018 (handle ConstValue::ByRef in relate) - rust-lang#71758 (Remove leftover chalk types) - rust-lang#71760 (Document unsafety for `*const T` and `*mut T`) - rust-lang#71761 (doc: reference does not exist, probably a typo) - rust-lang#71762 (doc: this resulted in a link pointing to a non-existent target) Failed merges: - rust-lang#71726 (Suggest deref when coercing `ty::Ref` to `ty::RawPtr` with arbitrary mutability) r? @ghost
Split out from #69406
Since the other PR is having memory problems with
parallel-compiler = true
, figured I should split this out. Surprisingly, this actually changes some errors, and I'm not quite sure why.r? @nikomatsakis