-
Notifications
You must be signed in to change notification settings - Fork 12.8k
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 (lots of) dead code #83185
Remove (lots of) dead code #83185
Conversation
r? @oli-obk (rust-highfive has picked a reviewer for you, use r? to override) |
This comment has been minimized.
This comment has been minimized.
86e1dd2
to
08e596a
Compare
@bors try @rust-timer queue I expect this to help hello-world, but not much else. |
Awaiting bors try build completion. @rustbot label: +S-waiting-on-perf |
⌛ Trying commit 08e596a84bea96a0d8c3799c36724c012bb9154b with merge cee392aca3bbc45102766189904bd3c29f498f19... |
This comment has been minimized.
This comment has been minimized.
08e596a
to
c6d3f5e
Compare
This comment has been minimized.
This comment has been minimized.
3dd122c
to
aa09c5b
Compare
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
Hmm, it seems likely that the resolution of some of our floating point bugs will require more architecture-awareness of floats, rather than less, but I guess if we aren't using it we could just resurrect the code from git history if that time comes... |
Please don't touch rustc_apfloat without conferring with @eddyb . They manually transpiled llvm's apfloat to Rust and this is the result. We should not touch that library afaik. |
So the whole deal with It shouldn't even be in-tree IMO, see also #55993 - people have wanted to use it elsewhere, too. But I haven't been able to do as much as I want with it because it's been stuck in licensing limbo for years. I don't dare to touch it at all, really, while the licensing situation is up in the air, in the fear that it will prolong the limbo (originally I was assured there were no licensing issues and whoever told me that was wrong, so I don't want that to happen again) and I'd strongly advise anyone else against messing with it. (Can we add a rule somewhere that makes Once the licensing situation is sorted out, and we can move it out of tree, publish on crates.io, etc. I want to take this "two main branches" approach, to cleanly separate what's "tracking LLVM upstream" and what's our own patches: #55993 (comment) |
impl<'tcx> ImpliedOutlivesBounds<'tcx> { | ||
pub fn new(ty: Ty<'tcx>) -> Self { | ||
ImpliedOutlivesBounds { ty } | ||
} | ||
} |
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.
cc @nikomatsakis unsure what's going on here.
I added back all the functions @oli-obk asked I keep, this should be ready for another round of review. |
Except for the sync stuff, everything lgtm. I have no strong opinion, but since I have good hopes that the work on parallel compiler will continue this year, I'm worried this removes things we'll just need to add again. I don't know who to ping about it right now though |
It looks like cc @Zoxc - do these changes to |
There isn't currently a good reviewer for these, and I don't want to remove things that will just be added again. I plan to make a separate PR for these changes so the rest of the cleanup can land.
I reverted the sync changes, I'll make a separate PR for them so they don't hold up everything else. @bors r=oli-obk |
📌 Commit 526bb10 has been approved by |
☀️ Test successful - checks-actions |
Remove dead or useless code from Session This is a more principled follow-up to rust-lang#83185 (comment). - Rename `Parser::span_fatal_err` -> `Parser::span_err` - Remove some unnecessary uses of `struct_span_fatal` - Make `Diagnostic::span_fatal` unconditionally raise an error - Add `impl Deref<Target = Handler>` for Session and remove all functions that are exactly the same as their Handler counterparts - Note why `Handler::fatal` is different from `Sesssion::fatal` - Remove unused `opt_span_warn` function r? `@oli-obk` or `@estebank`
Remove unused code from `rustc_data_structures::sync` Found using https://github.com/est31/warnalyzer. Follow-up to rust-lang#83185. r? `@Zoxc` cc `@oli-obk`
Make diagnostics clearer for `?` operators Re-submission of rust-lang#75029, fixes rust-lang#71309 This also revives the `content` methods removed by rust-lang#83185. r? `@estebank`
Builds on
DiagnosticBuilder::sub
function #83161forward_inner_docs
hack #83230Found with https://github.com/est31/warnalyzer.
See #77739 for a similar change in the past.
Dubious changes:
TODO:
cfg(test)
changes into Move some test-only code to test files #83197cc @est31