diff options
| author | bors <bors@rust-lang.org> | 2022-09-27 13:07:05 +0000 |
|---|---|---|
| committer | bors <bors@rust-lang.org> | 2022-09-27 13:07:05 +0000 |
| commit | 8805d05d01f961476b815e38ce054de1c950119d (patch) | |
| tree | e59a38a9a323821083ea4a01e306859dbfec2623 /tests/debuginfo/enum-thinlto.rs | |
| parent | b01cdd89d581b2580396b846784d92c1cc128e05 (diff) | |
| parent | 651c586035dfb4cf244aa9e9dacabfee9f579564 (diff) | |
| download | rust-8805d05d01f961476b815e38ce054de1c950119d.tar.gz rust-8805d05d01f961476b815e38ce054de1c950119d.zip | |
Auto merge of #13296 - Strum355:package-information-package-name, r=Veykril
Fix PackageInformation having the crate name instead of package name The `PackageInformation` type from the LSIF PR used the _crate_ name instead of the _package_ name. This caused issues when looking up crates by this name on the Sourcegraph backend, where we sync crate contents, for crates such as actix-web and many of its components (actix-files, actix-http etc etc), see screenshot 1 for the observed symptom. This PR hasnt been tested on other entry points besides cargo (such as project json). See screenshot 2 for the change in behaviour via SCIP snapshot comparison. <details> <summary>Screenshot 1</summary>  </details> <details> <summary>Screenshot 2</summary>  </details> Follow-up PR to my question over at the [rust-lang Zulip](https://rust-lang.zulipchat.com/#narrow/stream/185405-t-compiler.2Frust-analyzer/topic/canonical.20crate.20name.20confusion.20for.20monikers), excuse any incorrect usages of the term package vs crate.
Diffstat (limited to 'tests/debuginfo/enum-thinlto.rs')
0 files changed, 0 insertions, 0 deletions
