-
Notifications
You must be signed in to change notification settings - Fork 12.7k
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 RunCompiler::emitter
.
#102992
Remove RunCompiler::emitter
.
#102992
Conversation
This comment has been minimized.
This comment has been minimized.
4afc313
to
0665cba
Compare
compiler/rustc_driver/src/lib.rs
Outdated
/// Used by RLS. | ||
/// Has no uses within this repository, but is used by bjorn3 for "hooking | ||
/// rust-analyzer's VFS into rustc at some point for running rustc without | ||
/// having to save". (See #102759.) |
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 isn't used for this yet, but may be in the future.
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.
I have updated the comment accordingly.
Other than that, are you happy with this PR?
It's no longer used.
0665cba
to
641f824
Compare
@bors r+ |
☀️ Test successful - checks-actions |
Finished benchmarking commit (a03ca01): comparison URL. Overall result: no relevant changes - no action needed@rustbot label: -perf-regression Instruction countThis benchmark run did not return any relevant results for this metric. Max RSS (memory usage)This benchmark run did not return any relevant results for this metric. CyclesResultsThis is a less reliable metric that may be of interest but was not used to determine the overall result at the top of this comment.
Footnotes |
Please search for public APIs you want to remove/change before doing so. There was no need for this "cleanup", it's just a change for the sake of change, and now some level of control has been removed from custom drivers. Maybe all It looks like there's no way to capture the compiler output without abusing Might be easier to try to create a (Not expecting this to get reverted, hence the workarounds, but it would be nice to not have repeats in the future) |
Should have done that. My bad. @nnethercote do you want to revert this PR and add a comment about it's use? |
We've already worked around it, don't worry about a revert: Turns out that I got turned around and Like I said before, the more important point is that more care should be taken in the future. EDIT: btw I opened an issue for us moving off of these weird unit tests: |
After rust-lang#114104, `rust-gpu` is unable to create a custom `Emitter` as the bounds have changed to include `WriteColor`. I was able to work around this by adding `termcolor` as a direct dependency, but I believe this should be exposed as part of `rustc_errors` proper. See rust-lang#102992 for why `rust-gpu` needs to create a custom emitter.
Make `termcolor` types public in `rustc_errors` After rust-lang#114104, `rust-gpu` is unable to create a custom `Emitter` as the bounds have changed to include `WriteColor`. I was able to work around this by adding `termcolor` as a direct dependency, but I believe this should be exposed as part of `rustc_errors` proper. See rust-lang#102992 for why `rust-gpu` needs to create a custom emitter.
It's no longer used.
r? @bjorn3