tree aecbbdcdc749d3735e458bae8b00abe16ae3635c
parent 613c47065a3c3784af8041a1e200c998c71d03af
author Marcel Hlopko <hlopko@google.com> 1624523451 +0200
committer GitHub <noreply@github.com> 1624523451 +0200
gpgsig -----BEGIN PGP SIGNATURE-----
 
 wsBcBAABCAAQBQJg1EK7CRBK7hj4Ov3rIwAAFbYIAC9TooVA/3Dn5OtdC98NoFx3
 SyskYO98Tj5xb1A+fv7Qxcw8ey7ZatmfJzG3edElh2KENxxaZmWU1Vpn30M9aPs2
 1SGAoaYT4PgotbGdfQgIGinAmQ0esbp1CvBNUrJg+BcOxJwe1KbPNyjK8ZS/xAIM
 oqZ4pM1oP9sk5EZIqRa5aPYloUuLzltakxyTqq5JcH6OUYL05CIUodaNmea4S46T
 S0xL7jfpe/+oP2xajlrOtr/MlmW1KrAJT/KSVzL6bNFBQS0kJplYFNfSnMaelsOR
 /71WaL9HDtRy1yta4r9v/VmIe3xyHeNLpW8zqdgjfC4lARq4AWkG0vS/MS8r2NM=
 =ueI+
 -----END PGP SIGNATURE-----
 

Merge deps of related crates in Rust Analyzer support (#781)

It can happen a single source file is present in multiple crates - there can
  be a `rust_library` with a `lib.rs` file, and a `rust_test` for the `test`
  module in that file. Tests can declare more dependencies than what library
  had. Therefore we had to collect all `RustAnalyzerInfo`s for a given crate
  and take deps from all of them.

  There's one exception - if the dependency is the same crate name as the
  the crate being processed, we don't add it as a dependency to itself. This is
  common and expected - `rust_test.crate` pointing to the `rust_library`.