# Anyone using \`--extern-location\`? **URL:** \ **Category:** compiler\ **Created:** [April 15, 2022, 6:28pm UTC](https://internals.rust-lang.org/t/anyone-using-extern-location/16480 "2022-04-15T18:28:46Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![jsgf](https://sea2.discourse-cdn.com/flex002/user_avatar/internals.rust-lang.org/jsgf/32/703_2.png) [@jsgf](https://internals.rust-lang.org/u/jsgf)\ **Post date:** [April 15, 2022, 6:28pm UTC](https://internals.rust-lang.org/t/anyone-using-extern-location/16480/1 "2022-04-15T18:28:46Z")
I introduced it in [Implement `--extern-location` by jsgf · Pull Request #72603 · rust-lang/rust · GitHub](https://github.com/rust-lang/rust/pull/72603) in order to improve the diagnostics for `-Wunused-crate-dependencies`. It was very successful at this, but I really don't like either how complex the implementation is, or even the basic idea of effectively routing external tool data through `rustc`. The `--json unused-externs` mechanism which notifies when a crate is unused is functionally the same, and a much simpler impementation. I believe it's what Cargo is (or intends?) to use. I've adapted my tooling to use this mechanism. `--extern-location` was never stabilized, and as far as I know I'm the only person to have used it. I've put up PR [Remove `--extern-location` and all associated code by jsgf · Pull Request #96086 · rust-lang/rust · GitHub](https://github.com/rust-lang/rust/pull/96086) to remove it and all the associated code. This is your chance to save it if you really want it. ---
**Author:** ![system](https://sea2.discourse-cdn.com/flex002/user_avatar/internals.rust-lang.org/system/32/14092_2.png) [@system](https://internals.rust-lang.org/u/system)\ **Post date:** [July 14, 2022, 6:29pm UTC](https://internals.rust-lang.org/t/anyone-using-extern-location/16480/2 "2022-07-14T18:29:22Z")
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.