-
Notifications
You must be signed in to change notification settings - Fork 12.9k
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 --extern-location
and all associated code
#96086
Conversation
`--extern-location` was an experiment to investigate the best way to generate useful diagnostics for unused dependency warnings by enabling a build system to identify the corresponding build config. While I did successfully use this, I've since been convinced the alternative `--json unused-externs` mechanism is the way to go, and there's no point in having two mechanisms with basically the same functionality. This effectively reverts rust-lang#72603
r? @davidtwco (rust-highfive has picked a reviewer for you, use r? to override) |
I posted a to irlo in case someone is actually using this functionality, but AFAIK I'm the only one: https://internals.rust-lang.org/t/anyone-using-extern-location/16480 Also cc @petrochenkov @nikomatsakis as reviewers on #72603. |
Do we want to wait a little longer for anyone to tell us they are using this? r=me otherwise |
I think we're good to go. We can always revert this PR if someone really needs it. |
@bors r=davidtwco |
📌 Commit 1be1157 has been approved by |
…dtwco Remove `--extern-location` and all associated code `--extern-location` was an experiment to investigate the best way to generate useful diagnostics for unused dependency warnings by enabling a build system to identify the corresponding build config. While I did successfully use this, I've since been convinced the alternative `--json unused-externs` mechanism is the way to go, and there's no point in having two mechanisms with basically the same functionality. This effectively reverts rust-lang#72603
…dtwco Remove `--extern-location` and all associated code `--extern-location` was an experiment to investigate the best way to generate useful diagnostics for unused dependency warnings by enabling a build system to identify the corresponding build config. While I did successfully use this, I've since been convinced the alternative `--json unused-externs` mechanism is the way to go, and there's no point in having two mechanisms with basically the same functionality. This effectively reverts rust-lang#72603
Rollup of 6 pull requests Successful merges: - rust-lang#94493 (Improved diagnostic on failure to meet send bound on future in a foreign crate) - rust-lang#95809 (Fix typo in bootstrap.py) - rust-lang#96086 (Remove `--extern-location` and all associated code) - rust-lang#96089 (`alloc`: make `vec!` unavailable under `no_global_oom_handling`) - rust-lang#96122 (Fix an invalid error for a suggestion to add a slice in pattern-matching) - rust-lang#96142 (Stop using CRATE_DEF_INDEX outside of metadata encoding.) Failed merges: r? `@ghost` `@rustbot` modify labels: rollup
Summary: `--extern-location` was an experimental option in rustc to pass tool diagnostic information through rustc. It was used to pass location information for unused dependencies from Buck via rustc for consumption by rustfixdeps. This was removed in upstream rust in rust-lang/rust#96086 so remove support for it here. Reviewed By: cjhopman fbshipit-source-id: 3509c3b2680a3a86fc782839f2a12312674f9d52
--extern-location
was an experiment to investigate the best way togenerate useful diagnostics for unused dependency warnings by enabling a
build system to identify the corresponding build config.
While I did successfully use this, I've since been convinced the
alternative
--json unused-externs
mechanism is the way to go, andthere's no point in having two mechanisms with basically the same
functionality.
This effectively reverts #72603